Navigate the page to the list of available tasks a worker (executor) can apply to. Requires the user to be signed in as a worker; the route is guarded and will redirect to login if not.
AI agents call em_browse_tasks to retrieve information from Execution Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and displays task listings for workers to review. No data is modified, no code is executed, and no financial transactions occur. The authentication requirement (sign-in as worker) is a standard access control, not a side effect. This is unambiguously a Read operation with minimal blast radius if an AI agent accesses it, since it only views task information the user is already authorized to see.
From the tool's definition em_browse_tasks: 'Navigate the page to the list of available tasks a worker (executor) can apply to.' This is a read-only operation that retrieves and displays data (available tasks) without creating, modifying, deleting, or executing any code/commands.
Attacks that exploit this kind of access
Navigate the page to the list of available tasks a worker (executor) can apply to. Requires the user to be signed in as a worker; the route is guarded and will redirect to login if not. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.
Register the Execution Market MCP server in PolicyLayer and add a rule for em_browse_tasks: 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_browse_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the em_browse_tasks 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_browse_tasks. 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_browse_tasks 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →