vault_container_revoke
Revoke a vault container transfer ID. Once revoked, the transfer ID cannot be used again. Example: vault_container_revoke({ transferId:
This record as markdown: /tools/io-github-0nork-0nmcp/vault-container-revoke.md
What vault_container_revoke does on 0nmcp
AI agents call vault_container_revoke to permanently remove resources in 0nmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why vault_container_revoke is rated Critical
The tool irreversibly invalidates a transfer ID — explicitly stated as permanent ('cannot be used again'). This is a one-way destructive action that could disrupt or permanently block data/asset transfers, warranting a high severity rating.
From the tool's definition 'Revoke a vault container transfer ID. Once revoked, the transfer ID cannot be used again.'
Attacks that exploit this kind of access
The rule that runs vault_container_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vault_container_revoke, this is the rule to start with:
vault_container_revoke 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 0nmcp, apply this rule, and every vault_container_revoke call is checked against it from then on.
Questions about vault_container_revoke
Revoke a vault container transfer ID. Once revoked, the transfer ID cannot be used again. Example: vault_container_revoke({ transferId:. It is categorised as a Destructive tool in the 0nmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 0n MCP server in PolicyLayer and add a rule for vault_container_revoke: 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 0nmcp. Nothing to install.
vault_container_revoke 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 vault_container_revoke 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 vault_container_revoke. 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.
vault_container_revoke is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
Across the catalogue