Submit completed work as an agent executor. On auto-approval: - Calculates Fase 5 fees (13% platform fee) - Logs payment events to audit trail - Records fee breakdown in submission metadata On auto-rejection: - Records structured rejection feedback - Reverts task to accepted (agent can retry)
Part of the Execution Market server.
Free to start. No card required.
AI agents use em_submit_agent_work to create or modify resources in Execution Market. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call em_submit_agent_work repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Execution Market.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"em_submit_agent_work": {
"limits": [
{
"counter": "em_submit_agent_work_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Execution Market policy for all 38 tools.
These attack patterns abuse exactly the kind of access em_submit_agent_work gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit completed work as an agent executor. On auto-approval: - Calculates Fase 5 fees (13% platform fee) - Logs payment events to audit trail - Records fee breakdown in submission metadata On auto-rejection: - Records structured rejection feedback - Reverts task to accepted (agent can retry). 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_agent_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.
em_submit_agent_work 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_agent_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.
Set action: deny in the PolicyLayer policy for em_submit_agent_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.
em_submit_agent_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.
Deterministic rules across all 38 Execution Market tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.