calendar_delete_event

THE RISK

Critical Risk

Why calendar_delete_event needs a policy

Deletion of calendar events is an irreversible operation that cannot be undone through the tool itself. While the blast radius is limited to calendar events (not financial transactions or system-level data), the destructive nature of permanent data removal justifies the Destructive category and high severity. Confidence is high because the intent is explicit and unambiguous.

From the tool's definition Tool name includes 'delete' and description states 'Deletes an event from the specified Google Calendar' — this operation irreversibly removes calendar data.

Documented attack patterns abuse exactly the kind of access calendar_delete_event gives an agent:

POLICY

How to control calendar_delete_event

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Workspace Server, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_delete_event:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "calendar_delete_event"
  ]
}

calendar_delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MCP Google Workspace Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Google Workspace Server tools

Destructive gmail_delete_draft Deletes a Gmail draft message by its ID. This action cannot be undone. Write calendar_create_event Creates a new event in the specified Google Calendar. Write gmail_archive Archives a Gmail message by removing it from the inbox. Write gmail_bulk_archive Archives multiple Gmail messages by removing them from the inbox. Write gmail_bulk_save_attachments Saves multiple Gmail attachments to disk by their message IDs and attachment IDs in a sing Write gmail_create_draft Creates a draft email message from scratch in Gmail with specified recipient, subject, bod Read calendar_get_events Retrieves calendar events from the user\ Read calendar_list Lists all calendars accessible by the user. Call it before any other tool wheneve

All 16 MCP Google Workspace Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Google Workspace Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about calendar_delete_event

What does the calendar_delete_event tool do? +

Deletes an event from the specified Google Calendar. It is categorised as a Destructive tool in the MCP Google Workspace Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on calendar_delete_event? +

Register the MCP Google Workspace Server MCP server in PolicyLayer and add a rule for calendar_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 Server. Nothing to install.

What risk level is calendar_delete_event? +

calendar_delete_event is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit calendar_delete_event? +

Yes. Add a rate_limit block to the calendar_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.

How do I block calendar_delete_event completely? +

Set action: deny in the PolicyLayer policy for calendar_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.

What MCP server provides calendar_delete_event? +

calendar_delete_event is provided by the MCP Google Workspace Server MCP server (j3k0/mcp-google-workspace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Google Workspace Server tool call.

Start from MCP Google Workspace Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →