Return high-level metadata about Execution Market — the Universal Execution Layer. Useful for agents that just landed on the page and need orientation (endpoints, on-chain identity, supported networks).
AI agents call em_site_info 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.
This tool retrieves static or semi-static information about the platform (endpoints, network support, identity metadata) without creating, modifying, deleting, or executing any operations. It is purely informational and defensive in nature—appropriate for new agents to orient themselves. No financial transactions, state mutations, or external command execution occur.
From the tool's definition Tool description explicitly states it 'Return[s] high-level metadata about Execution Market' and is 'Useful for agents that just landed on the page and need orientation'.
Attacks that exploit this kind of access
Return high-level metadata about Execution Market — the Universal Execution Layer. Useful for agents that just landed on the page and need orientation (endpoints, on-chain identity, supported networks). 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_site_info: 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_site_info 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_site_info 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_site_info. 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_site_info 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 →