em_submit_work

A write tool on the Execution Market MCP server.

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-submit-work.md

WHAT IT DOES

What em_submit_work does on Execution Market

AI agents use em_submit_work 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.

RISK

Why em_submit_work is rated Medium

This tool submits work product within a bounty/task system tied to financial payments (USDC). While the description is empty, the context—gasless USDC payments, escrow state checking, task approval workflows—suggests work submission commits or modifies a record that triggers downstream financial transactions.

From the tool's definition Tool name 'em_submit_work' in a task execution platform with USDC payments via x402; sibling tools include 'em_approve_submission' and 'em_assign_task' indicating a workflow for work submission and approval.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

em_submit_work Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "em_submit_work": {
      "limits": [
        {
          "counter": "em_submit_work_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_submit_work call is checked against it from then on.

FAQ

Questions about em_submit_work

What does the em_submit_work tool do? +

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

How do I enforce a policy on em_submit_work? +

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

em_submit_work is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit em_submit_work? +

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

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

em_submit_work 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

Govern customer-ops agents →Argument validation →Scoped token →