em_browse_agent_tasks

Browse tasks available for agent (or robot) execution.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-browse-agent-tasks.md

WHAT IT DOES

What em_browse_agent_tasks does on Execution Market

AI agents call em_browse_agent_tasks 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.

RISK

Why em_browse_agent_tasks is rated Low

This is a read-only operation that retrieves and displays available tasks. It has no side effects, does not execute code, does not move funds, and does not modify data. The blast radius of misuse is minimal—an agent could only over-query or enumerate tasks, which poses low risk.

From the tool's definition Tool name and description indicate browsing/querying tasks: 'Browse tasks available for agent (or robot) execution.' No modification, deletion, payment, or code execution occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

em_browse_agent_tasks Allowed

em_browse_agent_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "em_browse_agent_tasks": {}
  }
}

ALLOW ONLY 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_browse_agent_tasks call is checked against it from then on.

FAQ

Questions about em_browse_agent_tasks

What does the em_browse_agent_tasks tool do? +

Browse tasks available for agent (or robot) execution. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on em_browse_agent_tasks? +

Register the Execution Market MCP server in PolicyLayer and add a rule for em_browse_agent_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.

What risk level is em_browse_agent_tasks? +

em_browse_agent_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit em_browse_agent_tasks? +

Yes. Add a rate_limit block to the em_browse_agent_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.

How do I block em_browse_agent_tasks completely? +

Set action: deny in the PolicyLayer policy for em_browse_agent_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.

What MCP server provides em_browse_agent_tasks? +

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

KEEP EXPLORING

More on Execution Market, and thousands of servers like it.

This server

All 81 Execution Market tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →