AI agents call outlook_delete_event to permanently remove resources in Outlook — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting calendar events is a destructive action that cannot be undone. Once an event is deleted, it is permanently removed from the calendar. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because unintended deletion of calendar events could disrupt meetings, appointments, and business operations, though the blast…
From the tool's definition Tool name 'outlook_delete_event' and description 'Delete a calendar event' explicitly perform an irreversible deletion operation on calendar data.
Documented attack patterns abuse exactly the kind of access outlook_delete_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook, and nothing reaches the server without passing your rules. This is the rule we recommend for outlook_delete_event:
{
"version": "1",
"default": "deny",
"hide": [
"outlook_delete_event"
]
}outlook_delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a calendar event. It is categorised as a Destructive tool in the Outlook MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Outlook MCP server in PolicyLayer and add a rule for outlook_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 Outlook. Nothing to install.
outlook_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 outlook_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 outlook_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.
outlook_delete_event is provided by the Outlook MCP server (xenoxilus/outlook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Outlook, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
43 Outlook tools catalogued and risk-classified — across an index of 43,000+ MCP servers.