em_escrow_dispute

A financial tool on the Execution Market MCP server.

SERVERExecution Market SOURCEhttps://mcp.execution.market/mcp/
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-escrow-dispute.md

What em_escrow_dispute does on Execution Market

AI agents use em_escrow_dispute 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_dispute is rated Critical

The tool name references 'escrow' and 'dispute', which in the context of this financial payment platform (USDC payments, escrow management) strongly implies it triggers or manages a dispute process over escrowed funds. Disputing escrow can freeze, redirect, or release financial assets, placing this in the Financial category with high severity.

From the tool's definition Tool name 'em_escrow_dispute' on a server described as handling 'Gasless USDC payments via x402' with escrow functionality. Sibling tools include 'em_approve_submission', 'em_check_escrow_state', suggesting financial escrow operations.

Questions about em_escrow_dispute

What does the em_escrow_dispute tool do? +

em_escrow_dispute 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.

How do I enforce a policy on em_escrow_dispute? +

Register the Execution Market MCP server in PolicyLayer and add a rule for em_escrow_dispute: 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.

What risk level is em_escrow_dispute? +

em_escrow_dispute is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit em_escrow_dispute? +

Yes. Add a rate_limit block to the em_escrow_dispute 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.

How do I block em_escrow_dispute completely? +

Set action: deny in the PolicyLayer policy for em_escrow_dispute. 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.

What MCP server provides em_escrow_dispute? +

em_escrow_dispute 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Execution Market's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.