em_escrow_release
A financial tool on the Execution Market MCP server.
This record as markdown: /tools/market-execution-execution-market/em-escrow-release.md
What em_escrow_release does on Execution Market
AI agents use em_escrow_release to commit financial operations through Execution Market, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why em_escrow_release is rated Critical
Releasing escrow funds is an irreversible financial operation that transfers USDC to a recipient. Given the server's explicit financial context (USDC payments, bounties, escrow management), this tool almost certainly moves money. Even with an empty description, the naming convention and server context make this a Financial/critical classification. Misuse could result in unauthorized fund transfers.
From the tool's definition Tool name 'em_escrow_release' combined with server context: 'Gasless USDC payments via x402' and sibling tools like 'em_approve_submission', 'em_check_escrow_state'. The name strongly implies releasing funds held in escrow.
Attacks that exploit this kind of access
The rule that runs em_escrow_release safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Execution Market, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For em_escrow_release, this is the rule to start with:
Any call to em_escrow_release is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every em_escrow_release call is checked against it from then on.
Questions about em_escrow_release
em_escrow_release is a financial tool on the Execution Market MCP server. It is categorised as a Financial tool in the Execution Market MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_escrow_release: 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 Execution Market. Nothing to install.
em_escrow_release 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 em_escrow_release 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 em_escrow_release. 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.
em_escrow_release is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Execution Market, and thousands of servers like it.
Across the catalogue