capital_intent_open
AI agents use capital_intent_open 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 name 'capital_intent_open' strongly implies opening a financial capital intent or commitment (e.g., a payment channel, staking position, or financial order). Given the server's financial context (payments, staking, bridges) and sibling tools, this is most likely a Financial category action. Description is empty, lowering confidence slightly.
From the tool's definition Tool name 'capital_intent_open' on a server described as handling 'wallet, identity, payments, inference, staking, bridges, verification, agents'; sibling tools include payment and staking-related functions.
Attacks that exploit this kind of access
capital_intent_open. 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_open: 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_open 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_open 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_open. 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_open 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 →