Cancel a scheduled Calendly event.
AI agents call calendly_cancel_event to permanently remove resources in Integrations MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a scheduled event is an irreversible action — once cancelled, the event is removed and attendees are notified. The cancellation cannot be undone (the original scheduled meeting is lost), making this Destructive. Misuse could disrupt meetings and damage professional relationships.
From the tool's definition Cancel a scheduled Calendly event
Attacks that exploit this kind of access
Cancel a scheduled Calendly event. It is categorised as a Destructive tool in the Integrations MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Integrations MCP server in PolicyLayer and add a rule for calendly_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 Integrations MCP. Nothing to install.
calendly_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 calendly_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 calendly_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.
calendly_cancel_event is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →