release_escrow
Release escrowed funds to the payee via a signed ReleaseEscrow transaction.
This record as markdown: /tools/network-tenzro-tenzro/release-escrow.md
What release_escrow does on Tenzro Ledger MCP
AI agents use release_escrow to commit financial operations through Tenzro Ledger MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why release_escrow is rated Critical
This tool moves money by releasing escrowed funds to a payee, which is an irreversible financial transaction. It directly commits a financial obligation/transfer, making it Financial category with critical severity due to the potential for misuse resulting in unauthorized fund transfers.
From the tool's definition Release escrowed funds to the payee via a signed ReleaseEscrow transaction
Attacks that exploit this kind of access
The rule that runs release_escrow 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 release_escrow, this is the rule to start with:
Any call to release_escrow is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every release_escrow call is checked against it from then on.
Questions about release_escrow
Release escrowed funds to the payee via a signed ReleaseEscrow transaction. 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 release_escrow: 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.
release_escrow 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 release_escrow 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 release_escrow. 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.
release_escrow 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.
Across the catalogue