This record as markdown: /tools/app-businys-mcp-server/cancel-invitation.md
What cancel_invitation does on Businys
AI agents call cancel_invitation to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_invitation is rated Critical
Cancelling an invitation is an irreversible action — the invitation token/record is invalidated and cannot be 'uncancelled'. The 'Owner only' restriction indicates it is a privileged, non-trivial operation. While the blast radius is moderate (limited to the specific invitation), the action cannot be undone, placing it in the Destructive category.
From the tool's definition Cancel a pending invitation. Owner only.
Attacks that exploit this kind of access
The rule that runs cancel_invitation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_invitation, this is the rule to start with:
cancel_invitation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every cancel_invitation call is checked against it from then on.
Questions about cancel_invitation
Cancel a pending invitation. Owner only. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for cancel_invitation: 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 Businys. Nothing to install.
cancel_invitation 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_invitation 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_invitation. 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_invitation is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue