AI agents call getWalletTransactionCount to retrieve information from MCP Ethers Wallet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name strongly suggests a data retrieval operation. Getting a transaction count is a read-only query of blockchain state with no side effects. The severity is low because unauthorized access to this data poses minimal direct harm—transaction counts are typically public blockchain information.
From the tool's definition Tool name 'getWalletTransactionCount' indicates a query operation that retrieves transaction count data from a wallet without modifying state. The pattern matches other read operations on this server (erc20_balanceOf, erc721_balanceOf, checkWalletExists).
Documented attack patterns abuse exactly the kind of access getWalletTransactionCount gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ethers Wallet, and nothing reaches the server without passing your rules. This is the rule we recommend for getWalletTransactionCount:
{
"version": "1",
"default": "deny",
"tools": {
"getWalletTransactionCount": {}
}
}getWalletTransactionCount 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.
getWalletTransactionCount. It is categorised as a Read tool in the MCP Ethers Wallet MCP Server, which means it retrieves data without modifying state.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for getWalletTransactionCount: 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 MCP Ethers Wallet. Nothing to install.
getWalletTransactionCount 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 getWalletTransactionCount 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 getWalletTransactionCount. 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.
getWalletTransactionCount is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ethers Wallet, 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.
69 MCP Ethers Wallet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.