High Risk →

proxy__eth_call

Executes a new message call immediately without creating a transaction on the block chain.

How to control proxy__eth_call ↓

What proxy__eth_call does on Etherscan MCP

AI agents invoke proxy__eth_call 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.

High Risk

Why proxy__eth_call needs a policy

The tool executes a call against the Ethereum blockchain (smart contract call). While it does not create a transaction or persist state changes on-chain, it does run arbitrary contract code. The word 'Executes' clearly places this in the Execute category.

From the tool's definition Executes a new message call immediately without creating a transaction on the block chain.

Documented attack patterns abuse exactly the kind of access proxy__eth_call gives an agent:

How to control proxy__eth_call

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_call:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxy__eth_call": {
      "limits": [
        {
          "counter": "proxy__eth_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

proxy__eth_call 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.

  1. Create a free account and register Etherscan MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about proxy__eth_call

What does the proxy__eth_call tool do? +

Executes a new message call immediately without creating a transaction on the block chain. 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.

How do I enforce a policy on proxy__eth_call? +

Register the Etherscan MCP server in PolicyLayer and add a rule for proxy__eth_call: 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.

What risk level is proxy__eth_call? +

proxy__eth_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit proxy__eth_call? +

Yes. Add a rate_limit block to the proxy__eth_call 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.

How do I block proxy__eth_call completely? +

Set action: deny in the PolicyLayer policy for proxy__eth_call. 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.

What MCP server provides proxy__eth_call? +

proxy__eth_call 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.

Enforce policy on every Etherscan MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.