em_get_payment_info

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-get-payment-info.md

WHAT IT DOES

What em_get_payment_info does on Execution Market

AI agents use em_get_payment_info 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_get_payment_info is rated Critical

The server context is explicitly financial (USDC payments, escrow). The tool name 'em_get_payment_info' suggests retrieval of payment information, which would normally be Read. However, given sibling tools that approve submissions and check escrow state, 'get_payment_info' could potentially trigger or initiate payment flows. The description is empty, reducing confidence.

From the tool's definition Tool name 'em_get_payment_info' on a server described as handling 'Gasless USDC payments via x402' with sibling tools like em_approve_submission and em_check_escrow_state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

em_get_payment_info Approval-gated

Any call to em_get_payment_info 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_get_payment_info": {
      "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_get_payment_info call is checked against it from then on.

FAQ

Questions about em_get_payment_info

What does the em_get_payment_info tool do? +

em_get_payment_info 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_get_payment_info? +

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

em_get_payment_info 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_get_payment_info? +

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

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

em_get_payment_info 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

request_x402_payment on Pop Pay →create_payment on Shopmonkey MCP Server →create_contract_payment on AdButler → All critical-risk MCP tools → The MCP Attack Database →

Guides

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