bridge_with_hook

Bridge tokens with a post-delivery hook to execute a contract call on the destination chain.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/bridge-with-hook.md

WHAT IT DOES

What bridge_with_hook does on Tenzro Ledger MCP

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.

RISK

Why bridge_with_hook is rated Critical

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

RECOMMENDED RULE

The rule that runs bridge_with_hook safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bridge_with_hook, this is the rule to start with:

bridge_with_hook Approval-gated

Any call to bridge_with_hook is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bridge_with_hook": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every bridge_with_hook call is checked against it from then on.

FAQ

Questions about bridge_with_hook

What does the bridge_with_hook tool do? +

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.

How do I enforce a policy on bridge_with_hook? +

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.

What risk level is bridge_with_hook? +

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.

Can I rate-limit bridge_with_hook? +

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.

How do I block bridge_with_hook completely? +

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.

What MCP server provides bridge_with_hook? +

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.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →