AI agents call getTransactionCount to retrieve information from Ethereum Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction count information without modifying, deleting, or executing any code. It has no side effects and fits the Read category pattern. No financial transactions occur. Severity is low because retrieving blockchain metrics poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'getTransactionCount' indicates a query operation that retrieves transaction count data from the Ethereum blockchain.
Documented attack patterns abuse exactly the kind of access getTransactionCount gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ethereum Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactionCount:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionCount": {}
}
}getTransactionCount 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.
getTransactionCount. It is categorised as a Read tool in the Ethereum Tools MCP Server, which means it retrieves data without modifying state.
Register the Ethereum Tools MCP server in PolicyLayer and add a rule for getTransactionCount: 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 Ethereum Tools. Nothing to install.
getTransactionCount 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 getTransactionCount 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 getTransactionCount. 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.
getTransactionCount is provided by the Ethereum Tools MCP server (0xgval/evm-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ethereum Tools, 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.
11 Ethereum Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.