Switch to a different connected Google account
AI agents use switch_account to create or update resources in Google Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Calendar MCP environment.
This tool changes application state by switching the active account context, which is a reversible modification. It does not retrieve data (Read), execute external commands (Execute), delete anything (Destructive), or move money (Financial).
From the tool's definition Tool name 'switch_account' and description 'Switch to a different connected Google account' indicate a state-changing operation that modifies which account is active.
Attacks that exploit this kind of access
Switch to a different connected Google account. It is categorised as a Write tool in the Google Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Calendar MCP server in PolicyLayer and add a rule for switch_account: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Calendar MCP. Nothing to install.
switch_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the switch_account rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for switch_account. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
switch_account is provided by the Google Calendar MCP server (paytience/google-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →