Get aggregate blockchain statistics including total blocks, transactions, addresses, and average block time.
AI agents call getStats to retrieve information from Agentek Eth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries public blockchain statistics. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. It falls squarely into the Read category with low severity since misuse would only result in information disclosure of already-public blockchain data.
From the tool's definition The tool description explicitly states it retrieves 'aggregate blockchain statistics including total blocks, transactions, addresses, and average block time.' These are read-only queries with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access getStats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for getStats:
{
"version": "1",
"default": "deny",
"tools": {
"getStats": {}
}
}getStats 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.
Get aggregate blockchain statistics including total blocks, transactions, addresses, and average block time. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getStats: 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 Agentek Eth. Nothing to install.
getStats 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 getStats 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 getStats. 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.
getStats is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentek Eth, 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.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.