This record as markdown: /tools/ark7-google-drive-mcp/deletecalendarevent.md
What deleteCalendarEvent does on Google Drive
AI agents call deleteCalendarEvent to permanently remove resources in Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
eventId | string | Yes | The event ID to delete |
calendarId | string | — | Calendar ID (default: primary) |
sendUpdates | string | — | Send cancellation notifications (default: none) |
Parameters from the server's own tool schema.
Why deleteCalendarEvent is rated Critical
This tool permanently removes calendar events, which cannot be undone. Deletion is irreversible data destruction, making it Destructive rather than Write. The severity is high because unauthorized deletion of calendar events could disrupt schedules, meetings, and coordination across an organization, though the blast radius is typically limited to calendar data rather than critical system infrastructure.
From the tool's definition Tool name is 'deleteCalendarEvent' with description 'Delete a calendar event'. The verb 'delete' combined with calendar event data indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteCalendarEvent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteCalendarEvent, this is the rule to start with:
deleteCalendarEvent 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 Drive, apply this rule, and every deleteCalendarEvent call is checked against it from then on.
Questions about deleteCalendarEvent
Delete a calendar event. It is categorised as a Destructive tool in the Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteCalendarEvent accepts 4 parameters: account, eventId, calendarId, sendUpdates. Required: eventId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for deleteCalendarEvent: 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 Drive. Nothing to install.
deleteCalendarEvent 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 deleteCalendarEvent 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 deleteCalendarEvent. 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.
deleteCalendarEvent is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
Across the catalogue