Release escrowed funds to the seller. Only the buyer can call this. Marks the deal as complete. Requires DEPLOYER_PRIVATE_KEY env var.
AI agents use release_escrow to commit financial operations through Base Escrow — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves real cryptocurrency funds (ETH or ERC-20 tokens) from escrow to the seller, constituting an irreversible financial transfer. It commits a financial obligation and cannot be undone once the blockchain transaction is confirmed. Misuse by an AI agent could result in funds being released to the wrong party or prematurely, causing direct financial loss.
From the tool's definition Release escrowed funds to the seller... Marks the deal as complete. Requires DEPLOYER_PRIVATE_KEY env var.
Attacks that exploit this kind of access
Release escrowed funds to the seller. Only the buyer can call this. Marks the deal as complete. Requires DEPLOYER_PRIVATE_KEY env var. It is categorised as a Financial tool in the Base Escrow MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Base Escrow 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 Base Escrow. 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 Base Escrow MCP server (lordbasilaiassistant-sudo/base-escrow-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 →