delete_calendar_event
Deletes an event from the Mac's Calendar app (Calendar.app) by ID. Requires confirm=true. For Microsoft 365 use m365_delete_event instead.
This record as markdown: /tools/com-local-mcp-local-mcp/delete-calendar-event.md
What delete_calendar_event does on Local
AI agents call delete_calendar_event to permanently remove resources in Local, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | Must be true to delete |
event_id | string | Yes | Event identifier from list_events |
Parameters from the server's own tool schema.
Why delete_calendar_event is rated Critical
This tool permanently removes calendar events without possibility of recovery through the tool itself. While the requirement for confirm=true provides a guard against accidental invocation, the underlying operation is irreversible deletion. Calendar events are user data that, once deleted, cannot be restored by the MCP tool.
From the tool's definition Deletes an event from the Mac's Calendar app (Calendar.app) by ID. The verb 'Deletes' and the irreversible nature of removing calendar events constitute destructive action.
Attacks that exploit this kind of access
The rule that runs delete_calendar_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_calendar_event, this is the rule to start with:
delete_calendar_event is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every delete_calendar_event call is checked against it from then on.
Questions about delete_calendar_event
Deletes an event from the Mac's Calendar app (Calendar.app) by ID. Requires confirm=true. For Microsoft 365 use m365_delete_event instead. It is categorised as a Destructive tool in the Local MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_calendar_event accepts 2 parameters: confirm, event_id. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for delete_calendar_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 Local. Nothing to install.
delete_calendar_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 delete_calendar_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 delete_calendar_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.
delete_calendar_event is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue