AI agents call deleteCalendar to permanently remove resources in MCP Apple Calendars — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on a calendar entity. Unlike deleteCalendarEvent (which removes individual events), deleteCalendar removes an entire calendar structure, potentially destroying multiple events and metadata at once. This cannot be undone and represents data loss. Classified as Destructive rather than Write because deletion is not reversible.
From the tool's definition Tool named 'deleteCalendar' with no description. Sibling tools include 'createCalendar', 'createCalendarEvent', 'deleteCalendarEvent', 'getCalendarEvents', establishing a calendaring context.
Documented attack patterns abuse exactly the kind of access deleteCalendar gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Apple Calendars, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteCalendar:
{
"version": "1",
"default": "deny",
"hide": [
"deleteCalendar"
]
} deleteCalendar disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
deleteCalendar. It is categorised as a Destructive tool in the MCP Apple Calendars MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Apple Calendars MCP server in PolicyLayer and add a rule for deleteCalendar: 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 Apple Calendars. Nothing to install.
deleteCalendar 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 deleteCalendar 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 deleteCalendar. 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.
deleteCalendar is provided by the MCP Apple Calendars MCP server (shadowfax92/apple-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Apple Calendars, 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.
7 MCP Apple Calendars tools catalogued and risk-classified — across an index of 43,000+ MCP servers.