delete-event
Remove event from calendar. Returns: empty on success. Use when: canceling appointments. Note: permanent deletion, not recoverable.
This record as markdown: /tools/199-biotechnologies-mcp-google/delete-event.md
What delete-event does on MCP Google Workspace
AI agents call delete-event to permanently remove resources in MCP Google Workspace, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-event is rated Critical
This tool irreversibly deletes calendar events with no undo capability. While the blast radius is limited to calendar data (not financial or system-wide), the permanent nature of deletion and potential to disrupt appointments/schedules places it in the Destructive category.
From the tool's definition Tool description explicitly states "permanent deletion, not recoverable" and the name "delete-event" indicates irreversible removal of calendar data.
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 Workspace, 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 Workspace, apply this rule, and every delete-event call is checked against it from then on.
Questions about delete-event
Remove event from calendar. Returns: empty on success. Use when: canceling appointments. Note: permanent deletion, not recoverable. It is categorised as a Destructive tool in the MCP Google Workspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Google Workspace 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 Workspace. 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 Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
Across the catalogue