Verify proofs / require all legs settled.
AI agents use capital_intent_verify to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The phrase 'all legs settled' strongly implies financial transaction settlement across multiple parties or chains (consistent with bridge/payment operations). While 'verify' sounds read-like, requiring settlement of financial legs is a financial commitment action.
From the tool's definition Verify proofs / require all legs settled — 'legs settled' implies multi-leg financial transactions or payment flows; combined with server context of 'wallet, payments, staking, bridges'
Attacks that exploit this kind of access
Verify proofs / require all legs settled. 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.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for capital_intent_verify: 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.
capital_intent_verify 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 capital_intent_verify 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 capital_intent_verify. 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.
capital_intent_verify 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.
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 →