getAddressNFTCollections
Get NFTs owned by an address, grouped by collection (ERC721/ERC1155).
This record as markdown: /tools/nanidao-agentek/getaddressnftcollections.md
What getAddressNFTCollections does on Agentek Eth
AI agents call getAddressNFTCollections 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 getAddressNFTCollections is rated Low
This tool queries blockchain state to retrieve NFT ownership data. It has no side effects, does not execute transactions, does not modify data, and does not create financial obligations. It is purely informational retrieval. The low severity reflects that unauthorized use would only expose publicly visible blockchain data (NFT ownership is publicly queryable on-chain).
From the tool's definition Tool description states 'Get NFTs owned by an address' — a retrieval operation with no modification, deletion, or execution of external code. The verb 'Get' and the passive phrasing 'owned by' indicate a read-only query.
Attacks that exploit this kind of access
The rule that runs getAddressNFTCollections 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 getAddressNFTCollections, this is the rule to start with:
getAddressNFTCollections 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 getAddressNFTCollections call is checked against it from then on.
Questions about getAddressNFTCollections
Get NFTs owned by an address, grouped by collection (ERC721/ERC1155). 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 getAddressNFTCollections: 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.
getAddressNFTCollections 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 getAddressNFTCollections 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 getAddressNFTCollections. 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.
getAddressNFTCollections 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