AI agents call delete_event to permanently remove resources in Google Calendar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of calendar events is an irreversible operation that permanently removes data. This fits the Destructive category definition: "irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push)." The severity is high because an AI agent with unchecked access could delete important calendar entries affecting meeting schedules, reminders, and coordination with other…
From the tool's definition Tool name and description explicitly state "Delete a calendar event" - a calendar event is data that, once deleted, cannot be recovered without manual restoration or backup access.
Documented attack patterns abuse exactly the kind of access delete_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Calendar MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_event:
{
"version": "1",
"default": "deny",
"hide": [
"delete_event"
]
}delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a calendar event. It is categorised as a Destructive tool in the Google Calendar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar MCP Server 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 Google Calendar MCP Server. 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 Google Calendar MCP Server MCP server (v-3/google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Google Calendar MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Google Calendar MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.