getAddressTokenTransfers

Read historical ERC20/ERC721/ERC1155 transfers and observed recipients sent or received by an address. Filter outgoing sender and exact NFT collection contract. Continue with continuation until supported explorer history is exhausted; incomplete pages cannot establish all recipients.

SERVERAgentek Eth SOURCEnanidao/agentek

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nanidao-agentek/getaddresstokentransfers.md

WHAT IT DOES

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.

RISK

Why getAddressTokenTransfers is rated Low

Tool retrieves historical blockchain transaction data without modifying or executing state changes.

From the tool's definition Read historical transfers, filter outgoing sender, observed recipients.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

getAddressTokenTransfers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getAddressTokenTransfers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about getAddressTokenTransfers

What does the getAddressTokenTransfers tool do? +

How do I enforce a policy on getAddressTokenTransfers? +

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.

What risk level is getAddressTokenTransfers? +

getAddressTokenTransfers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getAddressTokenTransfers? +

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.

How do I block getAddressTokenTransfers completely? +

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.

What MCP server provides getAddressTokenTransfers? +

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.

KEEP EXPLORING

More on Agentek Eth, and thousands of servers like it.

This server

All 212 Agentek Eth tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →