AI agents invoke proxy__eth_estimateGas to trigger actions in Etherscan MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
eth_estimateGas triggers a simulation of a transaction execution on the blockchain node. While it doesn't submit a real transaction, it runs code/transaction logic and has external operation side effects. The description is truncated ('which won') reducing confidence slightly, but the standard Ethereum eth_estimateGas behavior is well-known as a simulated execution call.
From the tool's definition 'eth_estimateGas' — executes a simulated call or transaction on the Ethereum network to estimate gas costs
Documented attack patterns abuse exactly the kind of access proxy__eth_estimateGas 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_estimateGas:
{
"version": "1",
"default": "deny",
"tools": {
"proxy__eth_estimateGas": {
"limits": [
{
"counter": "proxy__eth_estimategas_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} proxy__eth_estimateGas stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Makes a call or transaction, which won. It is categorised as a Execute tool in the Etherscan MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Etherscan MCP server in PolicyLayer and add a rule for proxy__eth_estimateGas: 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_estimateGas is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the proxy__eth_estimateGas 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_estimateGas. 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_estimateGas 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.