New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

eth_call

chainpeek: Call a smart contract function read-only on Ethereum, Base or Robinhood Chain. For gas units use estimate_gas; for a raw storage slot use get_storage_at. Returns the raw ABI-encoded return data (result, result_bytes) of eth_call against to with your calldata at latest, pending, finaliz...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 43 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/eth-call.md

What eth_call does on Tanod

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

ParameterTypeRequiredDescription
to string Yes Contract (or account) to call.
data string Yes ABI-encoded calldata, 0x-hex with an even number of digits, at most 8 kB (4-byte selector + arguments; 0x18160ddd is totalSupply()).
block object — latest (default), pending, finalized or a block number (older blocks need an archive node and may fail).
chain string Yes ethereum, base or robinhood (Robinhood Chain, chain id 4663).

Parameters from the server's own tool schema.

Why eth_call is rated Low

Even though eth_call only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about eth_call

What does the eth_call tool do? +

chainpeek: Call a smart contract function read-only on Ethereum, Base or Robinhood Chain. For gas units use estimate_gas; for a raw storage slot use get_storage_at. Returns the raw ABI-encoded return data (result, result_bytes) of eth_call against to with your calldata at latest, pending, finalized or a block number; nothing is signed or sent. The result is not decoded (decode_calldata decodes calldata; the ABI is yours). A call that reverts is a 422 reverted (not charged); results over 32 kB are a 502. Old blocks need an archive node and may fail. Ethereum, Base and Robinhood only; read-only: nothing is signed or sent. RPC reads are cached up to 30 s. A bad address, hash, hex string, block or range is a 422 before any payment (not charged). Typically under 1 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/ethereum-rpc-reads-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does eth_call accept? +

eth_call accepts 4 parameters: to, data, block, chain. Required: to, data, chain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on eth_call? +

Register the Tanod MCP server in PolicyLayer and add a rule for 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 Tanod. Nothing to install.

What risk level is eth_call? +

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

Can I rate-limit eth_call? +

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

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

eth_call is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tanod, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.