Returns the total number of discoverable Ethereum nodes.
AI agents call stats__nodecount to retrieve information from Etherscan MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves and returns a count statistic from Etherscan's blockchain data APIs. It has no side effects, does not execute code or transactions, does not modify data, and does not involve financial operations. The blast radius of misuse is minimal—an agent calling this tool repeatedly would at worst generate harmless query volume.
From the tool's definition Tool name 'stats__nodecount' and description 'Returns the total number of discoverable Ethereum nodes' indicate a read-only query operation that retrieves statistical data about the Ethereum network without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access stats__nodecount gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Etherscan MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stats__nodecount:
{
"version": "1",
"default": "deny",
"tools": {
"stats__nodecount": {}
}
} stats__nodecount is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the total number of discoverable Ethereum nodes. It is categorised as a Read tool in the Etherscan MCP MCP Server, which means it retrieves data without modifying state.
Register the Etherscan MCP server in PolicyLayer and add a rule for stats__nodecount: 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 Etherscan MCP. Nothing to install.
stats__nodecount 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 stats__nodecount 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 stats__nodecount. 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.
stats__nodecount is provided by the Etherscan MCP server (xiaok/etherscan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Etherscan MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Etherscan MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.