Delete a calendar
AI agents call calendar_delete_calendar to permanently remove resources in Google — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a calendar is an irreversible action that destroys all associated data. This falls clearly into the Destructive category, which takes precedence over Write. The severity is high because an AI agent accidentally invoking this could permanently erase a user's calendar and all events within it, with no undo capability.
From the tool's definition Tool name is 'calendar_delete_calendar' with description 'Delete a calendar'. The verb 'delete' combined with the scope (entire calendar) indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a calendar. It is categorised as a Destructive tool in the Google MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google MCP server in PolicyLayer and add a rule for calendar_delete_calendar: 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. Nothing to install.
calendar_delete_calendar 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 calendar_delete_calendar 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 calendar_delete_calendar. 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.
calendar_delete_calendar is provided by the Google MCP server (robcerda/google-mcp-server). 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 →