delete_event
Deletes (cancels) an event — there is no undelete. Deleting a series master id cancels the ENTIRE recurring series; deleting one instance id (from list_event_instances) cancels only that occurrence. On an event with guests this cancels the meeting for everyone, but cancellation emails go out only...
This record as markdown: /tools/a1-x-tech-mcp-google-calendar/delete-event.md
What delete_event does on Mcp Google Calendar
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | Yes | The event id from list_events or create_event output. A recurring-instance id (masterId_20260101T100000Z from list_event_instances) addresses one occurrence. |
calendar_id | string | Yes | The calendar id from list_calendars, or "primary" for the authenticated user's main calendar. |
send_updates | string | — | Who receives an email about this change: all guests, only guests outside your organization, or nobody. Defaults to none — attendees are NOT notified unless you |
Parameters from the server's own tool schema.
Why delete_event is rated Critical
An AI agent that decides to call delete_event doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Calendar is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_event, this is the rule to start with:
delete_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Calendar, apply this rule, and every delete_event call is checked against it from then on.
Questions about delete_event
Deletes (cancels) an event — there is no undelete. Deleting a series master id cancels the ENTIRE recurring series; deleting one instance id (from list_event_instances) cancels only that occurrence. On an event with guests this cancels the meeting for everyone, but cancellation emails go out only with send_updates=all. Returns {deleted:true}. 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.
delete_event accepts 3 parameters: event_id, calendar_id, send_updates. Required: event_id, calendar_id. The full parameter table on this page comes from the server's own tool schema.
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 (@a1-x-tech/mcp-google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Calendar, and thousands of servers like it.
Across the catalogue