AI agents call get_wallet_nft_positions to retrieve information from Zerion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about NFT holdings for a specified wallet. It performs a read-only operation similar to its sibling tools (get_wallet_balance_chart, get_wallet_fungible_positions, get_bitcoin_address_info). There is no data modification, deletion, execution of external code, or financial transaction involved.
From the tool's definition Tool name 'get_wallet_nft_positions' and description 'Get NFT positions held by a wallet' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Get NFT positions held by a wallet. It is categorised as a Read tool in the Zerion MCP Server, which means it retrieves data without modifying state.
Register the Zerion MCP server in PolicyLayer and add a rule for get_wallet_nft_positions: 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 Zerion. Nothing to install.
get_wallet_nft_positions 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 get_wallet_nft_positions 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 get_wallet_nft_positions. 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.
get_wallet_nft_positions is provided by the Zerion MCP server (rockyale/zerion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →