google-workspace.calendar_event_delete
Delete a Google Calendar event. Confirm with the user before calling.
This record as markdown: /tools/cowork-os/google-workspace.calendar-event-delete.md
What google-workspace.calendar_event_delete does on CoWork OS
AI agents call google-workspace.calendar_event_delete to permanently remove resources in CoWork OS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why google-workspace.calendar_event_delete is rated Critical
Deleting a calendar event is an irreversible operation that destroys data without possibility of recovery through the tool itself. While the description includes a safety measure ('Confirm with the user before calling'), the underlying action is destructive. The blast radius is high because a misused agent could delete many calendar events or critical meetings, causing schedule disruption and information loss.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a Google Calendar event'. This irreversibly removes calendar data.
Attacks that exploit this kind of access
The rule that runs google-workspace.calendar_event_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-workspace.calendar_event_delete, this is the rule to start with:
google-workspace.calendar_event_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 CoWork OS, apply this rule, and every google-workspace.calendar_event_delete call is checked against it from then on.
Questions about google-workspace.calendar_event_delete
Delete a Google Calendar event. Confirm with the user before calling. It is categorised as a Destructive tool in the CoWork OS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CoWork OS MCP server in PolicyLayer and add a rule for google-workspace.calendar_event_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 CoWork OS. Nothing to install.
google-workspace.calendar_event_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 google-workspace.calendar_event_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 google-workspace.calendar_event_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.
google-workspace.calendar_event_delete is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
Across the catalogue