em_check_submission

A read tool on the Execution Market MCP server.

SERVERExecution Market SOURCEhttps://mcp.execution.market/mcp/

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-check-submission.md

WHAT IT DOES

What em_check_submission does on Execution Market

AI agents call em_check_submission to retrieve information from Execution Market without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why em_check_submission is rated Low

Based on naming convention and context from sibling tools (em_browse_*, em_check_escrow_state), this appears to be a read operation that retrieves submission details without modifying state. The absence of action verbs like 'approve', 'reject', 'update', or 'delete' in the name suggests no side effects. However, confidence is moderate (0.6) due to the missing description, which would clarify intent.

From the tool's definition Tool name 'em_check_submission' suggests querying or verifying the status of a submission; the empty description prevents full confirmation of read-only behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

em_check_submission Allowed

em_check_submission is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "em_check_submission": {}
  }
}

ALLOW ONLY 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_check_submission call is checked against it from then on.

FAQ

Questions about em_check_submission

What does the em_check_submission tool do? +

em_check_submission is a read tool on the Execution Market MCP server. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on em_check_submission? +

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

em_check_submission is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit em_check_submission? +

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

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

em_check_submission 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →