Deletes an existing iCloud calendar event by its CalDAV URL.
AI agents call icloud-calendar_delete_event to permanently remove resources in Icloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of calendar data. Once deleted, an event cannot be recovered through the tool's API. The high severity reflects the potential for an AI agent to inadvertently remove important calendar entries (meetings, appointments) that could impact scheduling and personal/professional commitments. The confidence is high because the destructive intent is unambiguous in the description.
From the tool's definition Tool description explicitly states 'Deletes an existing iCloud calendar event' with irreversible action on user calendar data.
Attacks that exploit this kind of access
Deletes an existing iCloud calendar event by its CalDAV URL. It is categorised as a Destructive tool in the Icloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Icloud MCP server in PolicyLayer and add a rule for icloud-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 Icloud. Nothing to install.
icloud-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.
Yes. Add a rate_limit block to the icloud-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.
Set action: deny in the PolicyLayer policy for icloud-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.
icloud-calendar_delete_event is provided by the Icloud MCP server (thefredlab/icloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →