Get aggregate statistics: total chains, mainnets, testnets, L2s, beacons, and RPC health percentage
AI agents call get_stats to retrieve information from Chains API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns statistical summaries about blockchain chains and their health status. It performs no writes, deletions, code execution, or financial transactions. The data retrieved is informational only. The blast radius of misuse is minimal—an attacker could only obtain aggregate metrics about the blockchain ecosystem, which is typically public information.
From the tool's definition The tool description explicitly states it retrieves 'aggregate statistics' including 'total chains, mainnets, testnets, L2s, beacons, and RPC health percentage'.
Attacks that exploit this kind of access
Get aggregate statistics: total chains, mainnets, testnets, L2s, beacons, and RPC health percentage. It is categorised as a Read tool in the Chains API MCP Server, which means it retrieves data without modifying state.
Register the Chains API MCP server in PolicyLayer and add a rule for get_stats: 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 Chains API. Nothing to install.
get_stats 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 get_stats 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 get_stats. 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.
get_stats is provided by the Chains API MCP server (johnaverse/chains-api). 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 →