getAddressTokenTransfers
Get ERC20/ERC721/ERC1155 token transfers involving a specific address.
This record as markdown: /tools/nanidao-agentek/getaddresstokentransfers.md
What getAddressTokenTransfers does on Agentek Eth
AI agents call getAddressTokenTransfers 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 getAddressTokenTransfers is rated Low
This tool retrieves historical token transfer data for a given address. It queries blockchain state without creating transactions, modifying data, executing code, or moving funds. It is a read-only operation with minimal blast radius—the worst outcome of misuse would be information disclosure about an address's token activity, which is already public on the blockchain.
From the tool's definition Tool description states 'Get ERC20/ERC721/ERC1155 token transfers involving a specific address.' The verb 'Get' and the passive framing indicate data retrieval with no modification or execution of transactions.
Attacks that exploit this kind of access
The rule that runs getAddressTokenTransfers 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 getAddressTokenTransfers, this is the rule to start with:
getAddressTokenTransfers 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 getAddressTokenTransfers call is checked against it from then on.
Questions about getAddressTokenTransfers
Get ERC20/ERC721/ERC1155 token transfers involving 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 getAddressTokenTransfers: 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.
getAddressTokenTransfers 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 getAddressTokenTransfers 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 getAddressTokenTransfers. 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.
getAddressTokenTransfers 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