getTransactionLogs
Retrieve logs that were generated from a specific transaction.
This record as markdown: /tools/nanidao-agentek/gettransactionlogs.md
What getTransactionLogs does on Agentek Eth
AI agents call getTransactionLogs 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 getTransactionLogs is rated Low
This tool queries blockchain transaction data without side effects. It does not execute code, modify state, delete data, or move funds. The classification as Read is appropriate for a retrieval operation. Severity is low because misuse would only expose historical blockchain data already public on the ledger, with no destructive or financial impact.
From the tool's definition The tool 'getTransactionLogs' retrieves logs generated from a specific transaction. The verb 'retrieve' and the absence of any modification language (create, update, delete, execute) indicate a read-only operation.
Attacks that exploit this kind of access
The rule that runs getTransactionLogs 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 getTransactionLogs, this is the rule to start with:
getTransactionLogs 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 getTransactionLogs call is checked against it from then on.
Questions about getTransactionLogs
Retrieve logs that were generated from a specific transaction. 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 getTransactionLogs: 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.
getTransactionLogs 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 getTransactionLogs 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 getTransactionLogs. 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.
getTransactionLogs 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