em_submit_evidence
A write tool on the Execution Market MCP server.
This record as markdown: /tools/market-execution-execution-market/em-submit-evidence.md
What em_submit_evidence does on Execution Market
AI agents use em_submit_evidence to create or update resources in Execution Market, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Execution Market environment.
Why em_submit_evidence is rated Medium
This tool creates/modifies state by recording evidence submissions tied to task completions and financial outcomes (USDC bounty settlements). It is Write rather than Execute because it submits data rather than runs arbitrary code. It is high severity because incorrect or malicious evidence submission could trigger unwarranted payments or disputes in a financial system.
From the tool's definition Tool name em_submit_evidence suggests submission of evidence (likely proofs of work completion for bounty tasks); empty description limits certainty. Context shows gasless USDC payments via x402 and task acceptance/approval workflow.
Attacks that exploit this kind of access
The rule that runs em_submit_evidence 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_submit_evidence, this is the rule to start with:
em_submit_evidence stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every em_submit_evidence call is checked against it from then on.
Questions about em_submit_evidence
em_submit_evidence is a write tool on the Execution Market MCP server. It is categorised as a Write tool in the Execution Market MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_submit_evidence: 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_submit_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the em_submit_evidence 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_submit_evidence. 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_submit_evidence 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.
This server
Across the catalogue