evm_logs
Decoded event logs for any contract and event on Ethereum, Base, Arbitrum, OP Mainnet, Polygon or BNB Chain: give the event as a human signature (e.g. "Transfer(address indexed from, address indexed to, uint256 value)"), optional indexed-topic filters, and get the newest matching logs with named,...
This record as markdown: /tools/com-it-scorptech-x402/evm-logs.md
What evm_logs does on ScorpTech x402 API
AI agents call evm_logs to retrieve information from ScorpTech x402 API 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 | — | eth (default), base, arbitrum, optimism, polygon or bsc (chain ids and common aliases accepted) |
event | string | Yes | Event signature, e.g. "Swap(address indexed sender, uint256 amount0In, ...)". Mark indexed params; without "indexed" the first N params are assumed indexed from |
limit | integer | — | Max logs returned, newest first |
blocks | integer | — | Max blocks to scan back from toBlock |
topic1 | string | — | Filter on the 1st indexed param: address, uint (decimal) or 32-byte hex |
topic2 | string | — | Filter on the 2nd indexed param |
topic3 | string | — | Filter on the 3rd indexed param |
address | string | Yes | Contract address emitting the event (0x, 20 bytes) |
toBlock | integer | — | Newest block to scan (default head) |
Parameters from the server's own tool schema.
Why evm_logs is rated Low
Even though evm_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 evm_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For evm_logs, this is the rule to start with:
evm_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 ScorpTech x402 API, apply this rule, and every evm_logs call is checked against it from then on.
Questions about evm_logs
Decoded event logs for any contract and event on Ethereum, Base, Arbitrum, OP Mainnet, Polygon or BNB Chain: give the event as a human signature (e.g. "Transfer(address indexed from, address indexed to, uint256 value)"), optional indexed-topic filters, and get the newest matching logs with named, ABI-decoded arguments (exact integers as strings, checksummed addresses). Scans backwards from the head with an adaptive block window. Keyless public RPC. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/evm-logs. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
evm_logs accepts 9 parameters: chain, event, limit, blocks, topic1, topic2, topic3, address, toBlock. Required: event, address. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for evm_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 ScorpTech x402 API. Nothing to install.
evm_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 evm_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 evm_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.
evm_logs is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue