getAddressInternalTransactions
Get internal (trace-level) transactions for an address, including contract-to-contract calls and ETH transfers within transactions.
This record as markdown: /tools/nanidao-agentek/getaddressinternaltransactions.md
What getAddressInternalTransactions does on Agentek Eth
AI agents call getAddressInternalTransactions 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 getAddressInternalTransactions is rated Low
This tool performs read-only retrieval of transaction data from the Ethereum blockchain. It queries existing internal transactions and contract calls without creating, modifying, deleting, or executing any operations. The data retrieved is immutable historical information.
From the tool's definition Tool name 'getAddressInternalTransactions' and description explicitly state it 'Get[s] internal (trace-level) transactions for an address' — a query operation that retrieves historical blockchain data with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs getAddressInternalTransactions 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 getAddressInternalTransactions, this is the rule to start with:
getAddressInternalTransactions 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 getAddressInternalTransactions call is checked against it from then on.
Questions about getAddressInternalTransactions
Get internal (trace-level) transactions for an address, including contract-to-contract calls and ETH transfers within transactions. 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 getAddressInternalTransactions: 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.
getAddressInternalTransactions 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 getAddressInternalTransactions 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 getAddressInternalTransactions. 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.
getAddressInternalTransactions 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