Release escrowed funds to the worker after task approval. The on-chain flow: Escrow contract -> PaymentOperator.release() -> Worker USDC This is an irreversible operation. Once released, funds go directly to the worker's wallet. For dispute resolution after release, use em_escrow_dispute. Args: p...
Part of the Execution Market server.
Free to start. No card required.
AI agents may call em_escrow_release to permanently remove or destroy resources in Execution Market. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call em_escrow_release in a loop, permanently destroying resources in Execution Market. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"em_escrow_release"
]
}See the full Execution Market policy for all 38 tools.
These attack patterns abuse exactly the kind of access em_escrow_release gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Release escrowed funds to the worker after task approval. The on-chain flow: Escrow contract -> PaymentOperator.release() -> Worker USDC This is an irreversible operation. Once released, funds go directly to the worker's wallet. For dispute resolution after release, use em_escrow_dispute. Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.. It is categorised as a Destructive tool in the Execution Market MCP Server, which means it can permanently delete or destroy data. 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 Destructive 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.
Deterministic rules across all 38 Execution Market tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.