em_resolve_dispute
A financial tool on the Execution Market MCP server.
This record as markdown: /tools/market-execution-execution-market/em-resolve-dispute.md
What em_resolve_dispute does on Execution Market
AI agents use em_resolve_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_resolve_dispute is rated Critical
The server context involves USDC payments and escrow for real-world task bounties. Dispute resolution in such a context almost certainly involves adjudicating fund releases or reversals from escrow, making this a Financial action. The description is empty, reducing confidence, but the financial infrastructure of the server (USDC, escrow, bounties) strongly implies financial consequences.
From the tool's definition Tool name 'em_resolve_dispute' on a server described as handling 'Gasless USDC payments via x402' with escrow states and task bounties. Sibling tools include em_approve_submission, em_check_escrow_state, and em_cancel_task.
Attacks that exploit this kind of access
The rule that runs em_resolve_dispute 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_resolve_dispute, this is the rule to start with:
Any call to em_resolve_dispute 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_resolve_dispute call is checked against it from then on.
Questions about em_resolve_dispute
em_resolve_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.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_resolve_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.
em_resolve_dispute 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_resolve_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.
Set action: deny in the PolicyLayer policy for em_resolve_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.
em_resolve_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.
Across the catalogue