getAddressTransactions
Get the list of transactions sent from or received by a specific address.
This record as markdown: /tools/nanidao-agentek/getaddresstransactions.md
What getAddressTransactions does on Agentek Eth
AI agents call getAddressTransactions 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 getAddressTransactions is rated Low
This tool performs read-only access to blockchain transaction history. While cryptocurrency transaction data may be sensitive in some contexts, querying public blockchain data carries minimal direct risk of misuse by an AI agent. The tool cannot execute transactions, modify state, or move funds — it only retrieves information that is already publicly available on the Ethereum blockchain.
From the tool's definition Tool description states 'Get the list of transactions sent from or received by a specific address' — this is a query operation that retrieves historical transaction data without modifying, executing, or moving funds.
Attacks that exploit this kind of access
The rule that runs getAddressTransactions 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 getAddressTransactions, this is the rule to start with:
getAddressTransactions 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 getAddressTransactions call is checked against it from then on.
Questions about getAddressTransactions
Get the list of transactions sent from or received by a specific address. 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 getAddressTransactions: 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.
getAddressTransactions 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 getAddressTransactions 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 getAddressTransactions. 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.
getAddressTransactions 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