Delete a calendar event
AI agents call delete_event to permanently remove resources in Google Calendar MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a calendar event is a destructive action that cannot be undone. While not critical in the sense of financial loss or system compromise, the permanent removal of user calendar data constitutes a high-severity destructive operation. An AI agent with access to this tool could delete important events, meetings, or reminders without recovery, causing schedule disruption or loss of critical planning information.
From the tool's definition Tool name 'delete_event' and description 'Delete a calendar event' explicitly indicate irreversible removal of calendar data.
Attacks that exploit this kind of access
Delete a calendar event. It is categorised as a Destructive tool in the Google Calendar MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 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 Google Calendar MCP. 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 (paytience/google-calendar-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 →