Delete a calendar.
AI agents call delete_calendar to permanently remove resources in Gcalendar — 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 operation that cannot be undone—all calendar data, events, and metadata are permanently removed. This is the most severe category applicable (Destructive > Execute > Write > Read), with high severity due to the potential loss of important scheduling information and the inability to recover deleted content without external backups.
From the tool's definition Tool name 'delete_calendar' and description 'Delete a calendar' explicitly perform irreversible deletion of calendar data and all associated events.
Attacks that exploit this kind of access
Delete a calendar. It is categorised as a Destructive tool in the Gcalendar MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gcalendar MCP server in PolicyLayer and add a rule for 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 Gcalendar. Nothing to install.
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 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 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.
delete_calendar is provided by the Gcalendar MCP server (sandeepmallareddy/gcalendar-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 →