PlugsightDocs

Give your AI the least access it needs

Set up Plugsight so each AI app reaches only the accounts it needs and can change only what you mean it to, using the controls you already have.

The safest set-up gives each AI app exactly what its job needs and nothing more. Plugsight gives you five layers to do that. Use them from the outside in: first which accounts, then which items inside them, then what may change.

1. Connect only what you'll use

Each connection is a login Plugsight keeps for you. If you don't need an account, don't connect it, and remove connections you've stopped using (Connections → Remove). Removing a connection deletes its stored login straight away and takes it out of every MCP server.

2. Choose Selected accounts on each MCP server

All accounts is convenient for your own everyday server, but it grows by itself: every account you connect later is added. For anything else, choose Selected accounts and tick only what that server needs.

  • A server for client reporting: only that client's marketing connections.
  • A server for a dashboard or script: only the accounts it shows.
  • A server for support work: only the helpdesk and the support inbox.

To check what a server reaches, ask your AI "List my Plugsight accounts" in a chat that uses it. See Create an MCP server.

3. Hide items you never want in answers

One Google or Microsoft login often reaches many sites, properties, ad accounts, calendars or drives. On Connections, click Show sites & accounts (or Show drives, Show calendars) and switch off anything your AI should never use: test sites, closed clients, a private calendar.

Hidden items are hidden on every MCP server, even if your AI asks for them by name. See Choose which sites and accounts your AI can see.

4. Make servers read-only where you can

Untick Allow changes on any server that only needs to read. Its badge then says Read & draft only: through it, your AI can read and write email drafts, but can't send or change anything, whatever the account switches say.

Good candidates:

  • Reporting and analysis servers.
  • Servers used by scripts and dashboards, so their API key can't make changes.
  • A server you're using to test new prompts.

5. Turn on changes one account at a time

Every account's switch on Connections starts off: Drafts only for email, Read-only for helpdesk and calendars. Turn on only the accounts you need your AI to change, for example your work inbox but not your personal one.

Even with everything on, each change still waits for your approval in the chat. See How changes are allowed.

Some connectors only read

Marketing and analytics, contacts, files, stores and email marketing are read-only in Plugsight: your AI can never change them, whatever your settings. Google Ads and Merchant Center ask Google for broader permissions because Google offers no read-only option, but Plugsight only reads them. See Read-only connectors and Permissions Plugsight asks Google and Microsoft for.

Check your set-up

A quick review, every few months or when something changes:

  • Every connection on Connections is still needed.
  • Servers other than your own everyday one use Selected accounts.
  • Servers that only read have Allow changes unticked.
  • Only the accounts that need it have their switch on.
  • Every API key is still in use. Revoke the rest. See Keep app passwords and API keys safe.
  • AI apps connected on each server matches the apps you actually use. If not, use Disconnect all AI apps and reconnect the ones you use.