Delete a single calendar event by UID; for recurring events this removes the single occurrence only (EventKit
AI agents call ical__delete_event to permanently remove resources in Mcp Ical Swift — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes calendar events without reversibility. Although the deletion scope is limited to a single occurrence (and only one occurrence for recurring events), it still constitutes a destructive action that removes user data.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a single calendar event by UID'; the action irreversibly removes calendar data
Attacks that exploit this kind of access
Delete a single calendar event by UID; for recurring events this removes the single occurrence only (EventKit. It is categorised as a Destructive tool in the Mcp Ical Swift MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Ical Swift MCP server in PolicyLayer and add a rule for ical__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 Ical Swift. Nothing to install.
ical__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 ical__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 ical__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.
ical__delete_event is provided by the Mcp Ical Swift MCP server (sealjay/mcp-ical-swift). 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 →