eth_getCode

Retrieves the code at a given Ethereum address

SERVEREthereum RPC MCP Server SOURCE0xkoda/eth-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/0xkoda-eth-mcp/eth-getcode.md

WHAT IT DOES

What eth_getCode does on Ethereum RPC MCP Server

AI agents call eth_getCode to retrieve information from Ethereum RPC MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why eth_getCode is rated Low

This tool only retrieves/queries smart contract bytecode from the Ethereum blockchain. It performs no modifications, deletions, or financial transactions. It is a passive information retrieval operation, fitting the Read category. Severity is low because retrieving publicly available blockchain data poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'eth_getCode' and description 'Retrieves the code at a given Ethereum address' indicate a query-only operation with no side effects. This is a standard JSON-RPC read method.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs eth_getCode safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ethereum RPC MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eth_getCode, this is the rule to start with:

eth_getCode Allowed

eth_getCode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "eth_getCode": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ethereum RPC MCP Server, apply this rule, and every eth_getCode call is checked against it from then on.

FAQ

Questions about eth_getCode

What does the eth_getCode tool do? +

Retrieves the code at a given Ethereum address. It is categorised as a Read tool in the Ethereum RPC MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on eth_getCode? +

Register the Ethereum RPC MCP Server MCP server in PolicyLayer and add a rule for eth_getCode: 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 RPC MCP Server. Nothing to install.

What risk level is eth_getCode? +

eth_getCode is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit eth_getCode? +

Yes. Add a rate_limit block to the eth_getCode 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 eth_getCode completely? +

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

eth_getCode is provided by the Ethereum RPC MCP Server MCP server (0xkoda/eth-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ethereum RPC MCP Server, and thousands of servers like it.

This server

All 3 Ethereum RPC MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →