GOOGLESUPER_DELETE_EVENT
Deletes a specified event by event_id from a Google Calendar (calendar_id); this action is idempotent and raises a 404 error if the event is not found.
This record as markdown: /tools/googlesuper/googlesuper-delete-event.md
What GOOGLESUPER_DELETE_EVENT does on Google Super
AI agents call GOOGLESUPER_DELETE_EVENT to permanently remove resources in Google Super, 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 | — | Unique identifier of the event to delete, typically obtained upon event creation. |
calendar_id | string | — | Identifier of the Google Calendar (e.g., email address, specific ID, or 'primary' for the authenticated user's main calendar) from which the event will be delet |
Parameters from the server's own tool schema.
Why GOOGLESUPER_DELETE_EVENT is rated Critical
The tool permanently removes calendar events, which is an irreversible deletion operation. While not financial in nature, the destruction of calendar data (including meeting records, schedules, and commitments) can have significant downstream consequences for users and organizations. The idempotent nature confirms it performs actual deletion rather than soft-delete or archival.
From the tool's definition Deletes a specified event by `event_id` from a Google Calendar (`calendar_id`); this action is idempotent and raises a 404 error if the event is not found.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_DELETE_EVENT safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_DELETE_EVENT, this is the rule to start with:
GOOGLESUPER_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 Google Super, apply this rule, and every GOOGLESUPER_DELETE_EVENT call is checked against it from then on.
Questions about GOOGLESUPER_DELETE_EVENT
Deletes a specified event by event_id from a Google Calendar (calendar_id); this action is idempotent and raises a 404 error if the event is not found. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_DELETE_EVENT accepts 2 parameters: event_id, calendar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_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 Super. Nothing to install.
GOOGLESUPER_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 GOOGLESUPER_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 GOOGLESUPER_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.
GOOGLESUPER_DELETE_EVENT is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue