Delete an event from Google Calendar
AI agents call deleteEvent 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 a destructive operation that cannot be undone. An AI agent with access to this tool could maliciously or accidentally delete important calendar events for the user or others with whom the calendar is shared. The impact scales with calendar importance (work meetings, medical appointments, etc.).
From the tool's definition Tool name is 'deleteEvent' and description states 'Delete an event from Google Calendar'. This operation irreversibly removes data with no undo mechanism.
Attacks that exploit this kind of access
Delete an event from Google Calendar. 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 deleteEvent: 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.
deleteEvent 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 deleteEvent 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 deleteEvent. 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.
deleteEvent is provided by the Google Calendar MCP Server MCP server (naotaka3/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 →