Bridge tokens with a post-delivery hook to execute a contract call on the destination chain.
AI agents use bridge_with_hook to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves tokens across chains (cross-chain bridge), which constitutes a financial transaction moving assets. It also executes a contract call on the destination chain post-delivery, adding an Execute dimension. Per the severity rules, Financial > Execute, so it's classified as Financial.
From the tool's definition Bridge tokens with a post-delivery hook to execute a contract call on the destination chain
Attacks that exploit this kind of access
Bridge tokens with a post-delivery hook to execute a contract call on the destination chain. 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 bridge_with_hook: 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.
bridge_with_hook 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 bridge_with_hook 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 bridge_with_hook. 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.
bridge_with_hook 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 →