getTransactionInternalTransactions
Retrieve internal transactions that occurred within a given transaction.
This record as markdown: /tools/nanidao-agentek/gettransactioninternaltransactions.md
What getTransactionInternalTransactions does on Agentek Eth
AI agents call getTransactionInternalTransactions 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 getTransactionInternalTransactions is rated Low
This tool retrieves historical blockchain transaction data without creating, modifying, deleting, or executing any operations. Despite the server's automation context, this specific tool only queries existing Ethereum internal transactions. The read-only nature and absence of side effects classifies it as Read category with low severity, as misuse would only expose information already recorded on the blockchain.
From the tool's definition Tool name 'getTransactionInternalTransactions' and description 'Retrieve internal transactions' indicate a query/retrieval operation with no modification or execution capability. The verb 'Retrieve' explicitly denotes a read-only data access pattern.
Attacks that exploit this kind of access
The rule that runs getTransactionInternalTransactions 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 getTransactionInternalTransactions, this is the rule to start with:
getTransactionInternalTransactions 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 getTransactionInternalTransactions call is checked against it from then on.
Questions about getTransactionInternalTransactions
Retrieve internal transactions that occurred within a given 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 getTransactionInternalTransactions: 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.
getTransactionInternalTransactions 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 getTransactionInternalTransactions 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 getTransactionInternalTransactions. 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.
getTransactionInternalTransactions 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