Delete a Google Calendar event
AI agents call delete_event to permanently remove resources in Mcp Google Calendar — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes calendar events, which cannot be undone. Deletion is irreversible data destruction. While the blast radius is limited to calendar events (not system-critical), accidental or malicious deletion of important calendar entries (meetings, deadlines, commitments) could cause significant operational disruption.
From the tool's definition Tool name is 'delete_event' and description states 'Delete a Google Calendar event' - this directly performs irreversible deletion of calendar data.
Attacks that exploit this kind of access
Delete a Google Calendar event. It is categorised as a Destructive tool in the Mcp Google Calendar MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Google Calendar MCP server in PolicyLayer and add a rule for delete_event: 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 Mcp Google Calendar. Nothing to install.
delete_event 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_event 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_event. 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_event is provided by the Mcp Google Calendar MCP server (v01t/mcp-google-calendar). 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 →