Returns the number of transactions in a block.
How to control proxy__eth_getBlockTransactionCountByNumber ↓
AI agents call proxy__eth_getBlockTransactionCountByNumber 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 is a pure data retrieval function that queries Ethereum blockchain state to count transactions in a specific block. It performs no writes, deletions, code execution, or financial operations. The operation is read-only and has no side effects, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name 'eth_getBlockTransactionCountByNumber' and description 'Returns the number of transactions in a block' indicate a query operation that retrieves blockchain data without modification or side effects.
Documented attack patterns abuse exactly the kind of access proxy__eth_getBlockTransactionCountByNumber 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 proxy__eth_getBlockTransactionCountByNumber:
{
"version": "1",
"default": "deny",
"tools": {
"proxy__eth_getBlockTransactionCountByNumber": {}
}
} proxy__eth_getBlockTransactionCountByNumber 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 number of transactions in a block. 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 proxy__eth_getBlockTransactionCountByNumber: 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.
proxy__eth_getBlockTransactionCountByNumber 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 proxy__eth_getBlockTransactionCountByNumber 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 proxy__eth_getBlockTransactionCountByNumber. 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.
proxy__eth_getBlockTransactionCountByNumber 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.