em_view_agent_directory

Navigate to the public directory of registered agents (ERC-8004) operating on Execution Market.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/em-view-agent-directory.md

WHAT IT DOES

What em_view_agent_directory does on Execution Market

AI agents call em_view_agent_directory 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_view_agent_directory is rated Low

This tool retrieves public information about registered agents from a directory. It does not create, modify, delete, or execute any operations; it simply queries and displays existing public data. Even in the context of a financial/payments platform, viewing a public directory poses minimal risk — it is purely informational with no side effects or capability to affect funds, tasks, or system state.

From the tool's definition Tool name includes 'view' and description states 'Navigate to the public directory of registered agents' — a read-only retrieval of public directory information with no state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

em_view_agent_directory Allowed

em_view_agent_directory 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_view_agent_directory": {}
  }
}

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

FAQ

Questions about em_view_agent_directory

What does the em_view_agent_directory tool do? +

Navigate to the public directory of registered agents (ERC-8004) operating on Execution Market. 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_view_agent_directory? +

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

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

Can I rate-limit em_view_agent_directory? +

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

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

em_view_agent_directory 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 →