em_open_task
Open a specific task by ID in the agent task management view (shows details, applicants, and submissions).
This record as markdown: /tools/market-execution-execution-market/em-open-task.md
What em_open_task does on Execution Market
AI agents call em_open_task 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.
Why em_open_task is rated Low
The tool retrieves and displays information about a task including its details, applicants, and submissions. It is a read/view operation with no side effects on data or financial state.
From the tool's definition Open a specific task by ID in the agent task management view (shows details, applicants, and submissions)
Attacks that exploit this kind of access
The rule that runs em_open_task 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_open_task, this is the rule to start with:
em_open_task is read-only, so it stays allowed. 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_open_task call is checked against it from then on.
Questions about em_open_task
Open a specific task by ID in the agent task management view (shows details, applicants, and submissions). 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_open_task: 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_open_task 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_open_task 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_open_task. 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_open_task 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