Navigate to the Developers page (MCP tools reference, REST API, SDKs, skill.md links).
AI agents call em_view_developer_docs 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.
em_view_developer_docs retrieves and displays developer documentation. It performs no data modification, code execution, deletion, or financial transaction. The tool merely provides read access to technical reference materials. Even in the context of a payment/task platform, accessing documentation poses minimal risk and belongs in the Read category.
From the tool's definition Tool name and description indicate navigation to documentation pages: 'Navigate to the Developers page (MCP tools reference, REST API, SDKs, skill.md links)'. This is purely informational retrieval with no side effects.
Attacks that exploit this kind of access
Navigate to the Developers page (MCP tools reference, REST API, SDKs, skill.md links). 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_view_developer_docs: 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_view_developer_docs 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_view_developer_docs 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_view_developer_docs. 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_view_developer_docs 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 →