calendar_delete_event
AI agents call calendar_delete_event to permanently remove resources in M365 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting calendar events is an irreversible action that removes data and cannot be undone. This maps to the Destructive category per the classification rules. Severity is high because an AI agent invoking this without proper authorization or context could inadvertently delete important meetings, commitments, or scheduling information with business/personal impact.
From the tool's definition Tool name 'calendar_delete_event' directly indicates deletion of calendar events. The tool description is empty, providing no additional detail, but the name unambiguously describes a destructive operation that permanently removes data.
Attacks that exploit this kind of access
calendar_delete_event. It is categorised as a Destructive tool in the M365 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the M365 MCP server in PolicyLayer and add a rule for 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 M365. Nothing to install.
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 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 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.
calendar_delete_event is provided by the M365 MCP server (robin-collins/m365-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 →