GOOGLESUPER_CALENDARS_DELETE
Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars.
This record as markdown: /tools/googlesuper/googlesuper-calendars-delete.md
What GOOGLESUPER_CALENDARS_DELETE does on Google Super
AI agents call GOOGLESUPER_CALENDARS_DELETE 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 |
|---|---|---|---|
calendar_id | string | — | Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use |
Parameters from the server's own tool schema.
Why GOOGLESUPER_CALENDARS_DELETE is rated Critical
Deleting a calendar is a destructive action that cannot be undone and removes all associated data. While the blast radius is limited to secondary calendars rather than primary ones, it still constitutes irreversible data loss. This is more severe than Write (reversible modifications) and qualifies as Destructive per the classification rules.
From the tool's definition The tool description states it 'Deletes a secondary calendar,' which is an irreversible removal of data. The mention of using 'calendars.clear' for primary calendars reinforces that this tool performs deletion operations.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_CALENDARS_DELETE 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_CALENDARS_DELETE, this is the rule to start with:
GOOGLESUPER_CALENDARS_DELETE 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_CALENDARS_DELETE call is checked against it from then on.
Questions about GOOGLESUPER_CALENDARS_DELETE
Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars. 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_CALENDARS_DELETE accepts 1 parameter: 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_CALENDARS_DELETE: 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_CALENDARS_DELETE 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_CALENDARS_DELETE 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_CALENDARS_DELETE. 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_CALENDARS_DELETE 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