get_base_logs
Bounded eth_getLogs on Base (max 5-block span, 50 logs).
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-base-logs.md
What get_base_logs does on Delx MCP Server
AI agents call get_base_logs to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
topic0 | string | — | |
address | string | — | |
to_block | string | — | |
from_block | string | — |
Parameters from the server's own tool schema.
Why get_base_logs is rated Low
This tool queries Ethereum blockchain logs on the Base network with strict pagination limits. It retrieves data without side effects, aligning with the Read category. The bounded constraints further reduce any risk of resource exhaustion or abuse. Severity is low because log retrieval is a standard, read-only blockchain operation with no ability to modify state or execute code.
From the tool's definition Tool name 'get_base_logs' and description 'Bounded eth_getLogs on Base' indicate retrieval of blockchain logs. The function is explicitly bounded (max 5-block span, 50 logs), constraining query scope.
Attacks that exploit this kind of access
The rule that runs get_base_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_base_logs, this is the rule to start with:
get_base_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 Delx MCP Server, apply this rule, and every get_base_logs call is checked against it from then on.
Questions about get_base_logs
Bounded eth_getLogs on Base (max 5-block span, 50 logs). It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_base_logs accepts 4 parameters: topic0, address, to_block, from_block. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for get_base_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 Delx MCP Server. Nothing to install.
get_base_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_base_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_base_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_base_logs is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue