Critical Risk →

delete_event

Delete a calendar event.

How to control delete_event ↓

What delete_event does on Apple Shortcuts

AI agents call delete_event to permanently remove resources in Apple Shortcuts — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_event needs a policy

This tool permanently removes a calendar event, which cannot be undone. Deletion is irreversible data destruction, placing it in the Destructive category. Severity is high because an AI agent misusing this could accidentally delete important calendar entries (meetings, reminders, commitments), causing significant disruption and loss of scheduling information, though not involving financial or life-critical systems.

From the tool's definition Tool name is 'delete_event' and description states 'Delete a calendar event.' The verb 'delete' and explicit reference to removing a calendar event indicate irreversible data destruction.

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

How to control delete_event

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_event"
  ]
}

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 Apple Shortcuts — 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 delete_event

What does the delete_event tool do? +

Delete a calendar event. It is categorised as a Destructive tool in the Apple Shortcuts 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 delete_event? +

Register the Apple Shortcuts 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 Apple Shortcuts. Nothing to install.

What risk level is delete_event? +

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 delete_event? +

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.

How do I block delete_event completely? +

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.

What MCP server provides delete_event? +

delete_event is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apple Shortcuts tool call.

Start from Apple Shortcuts, 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.

423 Apple Shortcuts 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.