Dispatch a Hyperlane V3 message through the canonical Mailbox.
AI agents invoke hyperlane_dispatch to trigger actions in Tenzro Ledger MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Dispatching a cross-chain message via Hyperlane triggers an external cross-chain operation. While it may carry financial or destructive payloads depending on the message content, the base action is executing an external operation (sending a message through a cross-chain messaging protocol). The blast radius is high because misuse could trigger arbitrary cross-chain contract calls or asset transfers on remote chains.
From the tool's definition Dispatch a Hyperlane V3 message through the canonical Mailbox
Attacks that exploit this kind of access
Dispatch a Hyperlane V3 message through the canonical Mailbox. It is categorised as a Execute tool in the Tenzro Ledger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for hyperlane_dispatch: 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.
hyperlane_dispatch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hyperlane_dispatch 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 hyperlane_dispatch. 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.
hyperlane_dispatch 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 →