cross_vm_transfer

Perform an atomic cross-VM token transfer using the TNZO pointer model.

Server Tenzro Ledger MCP https://canton-mcp.tenzro.network/mcp
Category Financial
Risk class Critical
Parameters 00 required

What cross_vm_transfer does on Tenzro Ledger MCP

AI agents use cross_vm_transfer to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why cross_vm_transfer needs a policy

This tool directly moves cryptocurrency or tokens between virtual machines (likely blockchains), which constitutes a financial transaction. The 'atomic' nature indicates it cannot be partially reversed. An AI agent misusing this tool could transfer significant assets to unintended addresses or drain wallets, making this a critical-severity financial risk.

From the tool's definition 'cross_vm_transfer' performs 'atomic cross-VM token transfer' — this moves tokens/value across blockchain virtual machines, which is a financial operation that commits monetary obligations and transfers assets.

Questions about cross_vm_transfer

What does the cross_vm_transfer tool do? +

Perform an atomic cross-VM token transfer using the TNZO pointer model. It is categorised as a Financial tool in the Tenzro Ledger MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on cross_vm_transfer? +

Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for cross_vm_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 Tenzro Ledger MCP. Nothing to install.

What risk level is cross_vm_transfer? +

cross_vm_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cross_vm_transfer? +

Yes. Add a rate_limit block to the cross_vm_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.

How do I block cross_vm_transfer completely? +

Set action: deny in the PolicyLayer policy for cross_vm_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.

What MCP server provides cross_vm_transfer? +

cross_vm_transfer is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.