Critical Risk →

calendar__delete_event

Delete a calendar event

How to control calendar__delete_event ↓

What calendar__delete_event does on Proton-MCP

AI agents call calendar__delete_event to permanently remove resources in Proton-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why calendar__delete_event needs a policy

Deletion of calendar events cannot be undone and constitutes irreversible data loss. Even though the blast radius is limited to a user's calendar (not system-wide), the action is permanent and the severity warrants 'high' classification as a user may lose important scheduling information. Confidence is high because the intent is explicit in both name and description.

From the tool's definition Tool name contains 'delete' and description states 'Delete a calendar event' — this irreversibly removes calendar data.

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

How to control calendar__delete_event

PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, 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.

  1. Create a free account and register Proton-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about calendar__delete_event

What does the calendar__delete_event tool do? +

Delete a calendar event. It is categorised as a Destructive tool in the Proton-MCP 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 Proton- 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 Proton-MCP. 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 Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proton-MCP tool call.

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

Free to start. No card required.

36 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.