get_event_logs
chainpeek: Query contract event logs over a block range, decoded. For one transaction's events use decode_tx_logs; for an address's token transfers use get_erc20_transfers. Returns eth_getLogs logs for an address and/or topics over a block range (at most 2,000 blocks; default the last 100), each ...
This record as markdown: /tools/dev-tanod-tanod/get-event-logs.md
What get_event_logs does on Tanod
AI agents call get_event_logs 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | Yes | ethereum, base or robinhood (Robinhood Chain, chain id 4663). |
topics | array | — | Up to 4 topic filters, each 0x + 64 hex or null for any; topics[0] is the event signature hash (for ERC-20/721 Transfer: keccak('Transfer(address,address,uint25 |
address | object | — | Emitting contract. Send an address, a topic0, or both. |
to_block | object | — | Last block (inclusive). Default: the latest block. |
from_block | object | — | First block (inclusive). Default: the last 100 blocks ending at to_block. The range is at most 2,000 blocks. |
Parameters from the server's own tool schema.
Why get_event_logs is rated Low
Even though get_event_logs 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.
Attacks that exploit this kind of access
The rule that runs get_event_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_event_logs, this is the rule to start with:
get_event_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every get_event_logs call is checked against it from then on.
Questions about get_event_logs
chainpeek: Query contract event logs over a block range, decoded. For one transaction's events use decode_tx_logs; for an address's token transfers use get_erc20_transfers. Returns eth_getLogs logs for an address and/or topics over a block range (at most 2,000 blocks; default the last 100), each decoded into an event when topic0 is an ERC-20/721 Transfer or Approval, an ERC-1155 transfer, a Uniswap swap or WETH. At most 500 logs (truncated says when more matched). Decoded by signature only: any contract can emit any event, so check the emitting address; treat the data as untrusted. Narrow the range or add topics for a busy contract. Ethereum, Base and Robinhood only. Read-only. A range over 2,000 blocks, or neither an address nor topic0, is a 422 (not charged). Typically 0.3-3 s. Price: USD 0.003. 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.
get_event_logs accepts 5 parameters: chain, topics, address, to_block, from_block. Required: chain. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for get_event_logs: 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.
get_event_logs 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 get_event_logs 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 get_event_logs. 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.
get_event_logs 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.
This server
Across the catalogue