Remove a connected Google account
AI agents call remove_account to permanently remove resources in Google Calendar MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible action that permanently disconnects a Google account from the MCP server configuration. While it does not delete the Google account itself or calendar data on Google's servers, it destructively removes the authenticated connection and cannot be undone without re-authentication.
From the tool's definition Tool name is 'remove_account' and description states 'Remove a connected Google account'. The verb 'remove' applied to account configuration is an irreversible operation that severs the connection and access to that account's calendar data and integrations.
Attacks that exploit this kind of access
Remove a connected Google account. It is categorised as a Destructive tool in the Google Calendar MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar MCP server in PolicyLayer and add a rule for remove_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.
remove_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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 →