Returns the number of transactions sent from an address
AI agents call eth_getTransactionCount to retrieve information from EVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the transaction count for an address. It retrieves historical data from the blockchain with no ability to modify, delete, execute code, or move funds. The operation is informational only and poses minimal risk if called by an AI agent.
From the tool's definition Tool name 'eth_getTransactionCount' and description 'Returns the number of transactions sent from an address' indicate a query operation that retrieves blockchain data without side effects.
Attacks that exploit this kind of access
Returns the number of transactions sent from an address. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for eth_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 EVM MCP Server. Nothing to install.
eth_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 eth_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 eth_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.
eth_getTransactionCount is provided by the EVM MCP Server MCP server (jamesanz/evm-mcp). 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 →