Delete all events from a calendar.
AI agents call clear_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.
This tool permanently removes all events from a specified calendar without the ability to undo. The destruction is wholesale and cannot be recovered through the same interface, making it Destructive rather than merely Write. The high severity reflects the risk that an AI agent could accidentally or maliciously wipe entire calendar histories if manipulated into calling this tool without proper safeguards.
From the tool's definition Tool description explicitly states 'Delete all events from a calendar' — a bulk, irreversible deletion operation.
Attacks that exploit this kind of access
Delete all events from 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 clear_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.
clear_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 clear_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 clear_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.
clear_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 →