vault_container_transfer
Register a vault container transfer and get a transfer ID. Transfer IDs are unique and cannot be reused (replay prevention). Example: vault_container_transfer({ file:
This record as markdown: /tools/io-github-0nork-0nmcp/vault-container-transfer.md
What vault_container_transfer does on 0nmcp
AI agents use vault_container_transfer to commit financial operations through 0nmcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why vault_container_transfer is rated Critical
A 'vault container transfer' in the context of a universal API orchestrator most likely involves moving digital assets, funds, or secured valuables between accounts or containers. The emphasis on unique IDs and replay prevention suggests this prevents double-spending or duplicate transfers—hallmarks of financial operations.
From the tool's definition Tool name includes 'vault' and 'transfer'; description states it registers a vault container transfer and generates unique transfer IDs with replay prevention—architectural patterns typical of financial/asset movement systems.
Attacks that exploit this kind of access
The rule that runs vault_container_transfer 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_transfer, this is the rule to start with:
Any call to vault_container_transfer is blocked until a human approves 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_transfer call is checked against it from then on.
Questions about vault_container_transfer
Register a vault container transfer and get a transfer ID. Transfer IDs are unique and cannot be reused (replay prevention). Example: vault_container_transfer({ file:. It is categorised as a Financial tool in the 0nmcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the 0n MCP server in PolicyLayer and add a rule for vault_container_transfer: 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_transfer is a Financial 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_transfer 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_transfer. 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_transfer 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