cancel_workspace_invitation
Cancel one pending invitation in an explicitly verified Sanka workspace. Call current_workspace immediately before this tool and pass its internal workspace_id as expected_workspace_id. The tool and API both block on a mismatch. Explicit confirmation is required.
This record as markdown: /tools/sankahq-sanka-mcp/cancel-workspace-invitation.md
What cancel_workspace_invitation does on Sanka MCP Server
AI agents call cancel_workspace_invitation to permanently remove resources in Sanka MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_workspace_invitation is rated Critical
Cancelling a workspace invitation is an irreversible action — the invitation is permanently revoked. The recipient would need to be re-invited explicitly. This cannot be undone, placing it firmly in the Destructive category. The severity is high because misuse could lock out intended collaborators from a workspace, with organizational impact.
From the tool's definition Cancel one pending invitation... Explicit confirmation is required. The tool and API both block on a mismatch.
Attacks that exploit this kind of access
The rule that runs cancel_workspace_invitation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_workspace_invitation, this is the rule to start with:
cancel_workspace_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 Sanka MCP Server, apply this rule, and every cancel_workspace_invitation call is checked against it from then on.
Questions about cancel_workspace_invitation
Cancel one pending invitation in an explicitly verified Sanka workspace. Call current_workspace immediately before this tool and pass its internal workspace_id as expected_workspace_id. The tool and API both block on a mismatch. Explicit confirmation is required. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for cancel_workspace_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 Sanka MCP Server. Nothing to install.
cancel_workspace_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_workspace_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_workspace_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_workspace_invitation is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
Across the catalogue