em_escrow_charge

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-charge.md

WHAT IT DOES

What em_escrow_charge does on Execution Market

AI agents use em_escrow_charge to commit financial operations through Execution Market, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why em_escrow_charge is rated Critical

The tool operates on a financial system managing USDC (stablecoin) payments. An 'escrow_charge' function directly moves or commits funds held in escrow, which is a Financial category action. Misuse by an AI agent could result in unauthorized cryptocurrency transfers, making this critical severity.

From the tool's definition Server description states 'Gasless USDC payments via x402' and tool name 'em_escrow_charge' indicates a charge/debit operation on an escrow account holding cryptocurrency.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs em_escrow_charge 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_charge, this is the rule to start with:

em_escrow_charge Approval-gated

Any call to em_escrow_charge is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "em_escrow_charge": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every em_escrow_charge call is checked against it from then on.

FAQ

Questions about em_escrow_charge

What does the em_escrow_charge tool do? +

em_escrow_charge 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_charge? +

Register the Execution Market MCP server in PolicyLayer and add a rule for em_escrow_charge: 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_charge? +

em_escrow_charge 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_charge? +

Yes. Add a rate_limit block to the em_escrow_charge 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_charge completely? +

Set action: deny in the PolicyLayer policy for em_escrow_charge. 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_charge? +

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

KEEP EXPLORING

More on Execution Market, and thousands of servers like it.

This server

All 81 Execution Market tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →