Remove (delete) an invitee's data from a Calendly event.
AI agents call calendly_remove_invitee 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.
This tool permanently deletes invitee information from a Calendly event, which cannot be undone. While the blast radius is limited to a single event's invitee records (not company-wide deletion), the irreversible nature of data destruction places it in the Destructive category rather than Write.
From the tool's definition Tool name and description explicitly state 'Remove (delete) an invitee's data from a Calendly event.' The use of 'delete' combined with removal of invitee data indicates irreversible data destruction.
Attacks that exploit this kind of access
Remove (delete) an invitee's data from a 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_remove_invitee: 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_remove_invitee 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_remove_invitee 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_remove_invitee. 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_remove_invitee 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 →