m365_delete_event
Delete a calendar event from your Microsoft 365 / Outlook calendar by its ID.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-delete-event.md
What m365_delete_event does on Local
AI agents call m365_delete_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 |
|---|---|---|---|
id | string | Yes | Event ID from m365_list_events |
confirm | boolean | Yes | Set to true to confirm deletion (required) |
Parameters from the server's own tool schema.
Why m365_delete_event is rated Critical
This tool permanently removes calendar data without the ability to undo the action through normal tool usage. Deleting calendar events is irreversible and represents data loss. While the blast radius is limited to a user's calendar (not organization-wide destruction), the destructive nature of the action and potential for misuse by an AI agent (e.g., deleting important meetings) warrants 'high' severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a calendar event...by its ID'. The verb 'delete' and the action of removing a calendar event from Microsoft 365/Outlook indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs m365_delete_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 m365_delete_event, this is the rule to start with:
m365_delete_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 m365_delete_event call is checked against it from then on.
Questions about m365_delete_event
Delete a calendar event from your Microsoft 365 / Outlook calendar by its ID. 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.
m365_delete_event accepts 2 parameters: id, confirm. Required: id, confirm. 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 m365_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 Local. Nothing to install.
m365_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 m365_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 m365_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.
m365_delete_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