Permissions & safety
How Plugsight keeps your AI to reading until you allow more, and every control you have over what it may change.
Your AI can always read the accounts an MCP server reaches, and write email drafts. Sending email, changing helpdesk tickets and booking calendar events are off until you allow them, and each one then waits for your yes in the chat.
The controls at a glance
| Control | Where | What it does |
|---|---|---|
| Account switch | Connections, under Write access | The everyday setting: may the AI change things with this one account? Starts off for every account. |
| Allow changes | MCP servers → a server → Edit configuration | Untick it to make a server read-only, whatever the account switches say. |
| Approval in the chat | Your AI app | The AI shows you the exact email or change and waits for your yes. |
| Pause and Pause everything | Permissions | An emergency stop for one type of change, or all of them at once. |
| Daily email limit | Permissions → Daily email limit | How many emails each account may send in a rolling 24 hours. 20 by default. |
| Your plan | Billing | Sending and other changes are part of the Pro and Agency plans. |
| Activity | Activity | A record of every sign-in, settings change, read and write, kept for one year. |
In this section
- How changes are allowed: every condition that must be met before your AI can send or change anything.
- Switch states under each account: what Ready, Paused, Off, Not in any MCP server and Not yet mean.
- Pause changes: the emergency stop, the red notice and Resume.
- Read-only connectors: the types of account your AI can never change.
- Daily email limit: how the rolling 24-hour limit works and how to change it.
- Approvals in the chat: how your AI asks before each change.
- When a change is blocked: the exact messages your AI receives, and the fix for each.
- Activity log: what's recorded, the filters, and what Succeeded, Blocked and Failed mean.
Was this page helpful?