Remove a member from the organisation by revoking their seat. Prefer cuecrux_session as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the s...
Risk signalsBulk/mass operation — affects multiple targets
Part of the VaultCrux Memory Core server.
Free to start. No card required.
AI agents may call revoke_seat to permanently remove or destroy resources in VaultCrux Memory Core. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call revoke_seat in a loop, permanently destroying resources in VaultCrux Memory Core. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"revoke_seat"
]
}See the full VaultCrux Memory Core policy for all 76 tools.
These attack patterns abuse exactly the kind of access revoke_seat gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Remove a member from the organisation by revoking their seat. Prefer cuecrux_session as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.. It is categorised as a Destructive tool in the VaultCrux Memory Core MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VaultCrux Memory Core MCP server in PolicyLayer and add a rule for revoke_seat: 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 VaultCrux Memory Core. Nothing to install.
revoke_seat 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 revoke_seat 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 revoke_seat. 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.
revoke_seat is provided by the VaultCrux Memory Core MCP server (https://api.vaultcrux.com/platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 76 VaultCrux Memory Core tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.