getAddressLogs
Get event logs emitted by a specific address (useful for tracking contract events).
This record as markdown: /tools/nanidao-agentek/getaddresslogs.md
What getAddressLogs does on Agentek Eth
AI agents call getAddressLogs to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getAddressLogs is rated Low
This tool retrieves historical event logs from a blockchain address. Reading logs is a read-only operation that queries existing blockchain state without modifying data, executing code, or triggering financial transactions. It poses minimal risk as it only exposes information already publicly available on the blockchain.
From the tool's definition Tool description states 'Get event logs emitted by a specific address' which is a retrieval/query operation with no side effects. The phrase 'Get' and 'tracking' indicates passive data inspection rather than modification or execution.
Attacks that exploit this kind of access
The rule that runs getAddressLogs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getAddressLogs, this is the rule to start with:
getAddressLogs 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 Agentek Eth, apply this rule, and every getAddressLogs call is checked against it from then on.
Questions about getAddressLogs
Get event logs emitted by a specific address (useful for tracking contract events). It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getAddressLogs: 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 Agentek Eth. Nothing to install.
getAddressLogs 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 getAddressLogs 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 getAddressLogs. 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.
getAddressLogs is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue