Retrieve logs that were generated from a specific transaction.
AI agents call getTransactionLogs to retrieve information from Agentek Eth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access getTransactionLogs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactionLogs:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionLogs": {}
}
}getTransactionLogs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Agentek Eth, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.