Cancels a calendar event
AI agents call cancel-event to permanently remove resources in Outlook Assistant — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a calendar event sends cancellation notices to all attendees and removes the event from all participants' calendars. This action is effectively irreversible — once cancelled and notifications are sent, the damage to scheduled meetings and attendee expectations cannot be undone programmatically. This qualifies as Destructive, with high severity given it can disrupt meetings across multiple people.
From the tool's definition 'Cancels a calendar event' — cancellation of a calendar event is an irreversible action that notifies all attendees and removes the event, which cannot be undone.
Attacks that exploit this kind of access
Cancels a calendar event. It is categorised as a Destructive tool in the Outlook Assistant MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Outlook Assistant MCP server in PolicyLayer and add a rule for cancel-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 Assistant. Nothing to install.
cancel-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 cancel-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 cancel-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.
cancel-event is provided by the Outlook Assistant MCP server (titanzero/outlook-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 →