debridge_create_tx
Create a cross-chain transaction via deBridge DLN. Returns transaction data ready for signing.
This record as markdown: /tools/network-tenzro-tenzro/debridge-create-tx.md
What debridge_create_tx does on Tenzro Ledger MCP
AI agents use debridge_create_tx to create or update resources in Tenzro Ledger MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
Why debridge_create_tx is rated Medium
An AI agent can call debridge_create_tx faster than any human can review: one bad instruction and it creates or modifies resources in Tenzro Ledger MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs debridge_create_tx 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 debridge_create_tx, this is the rule to start with:
debridge_create_tx stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every debridge_create_tx call is checked against it from then on.
Questions about debridge_create_tx
Create a cross-chain transaction via deBridge DLN. Returns transaction data ready for signing. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for debridge_create_tx: 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.
debridge_create_tx is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the debridge_create_tx 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 debridge_create_tx. 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.
debridge_create_tx 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue