Retrieve count of unique buyers and sellers for NFT collections.
AI agents call get_unique_traders_by_collection to retrieve information from Nft Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics metrics (count of unique traders) from the Dune Analytics backend without creating, modifying, deleting, executing code, or moving financial assets. It is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_unique_traders_by_collection' and description 'Retrieve count of unique buyers and sellers for NFT collections' indicate data retrieval with no modification or execution capabilities.
Attacks that exploit this kind of access
Retrieve count of unique buyers and sellers for NFT collections. It is categorised as a Read tool in the Nft Analytics MCP Server, which means it retrieves data without modifying state.
Register the Nft Analytics MCP server in PolicyLayer and add a rule for get_unique_traders_by_collection: 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 Nft Analytics. Nothing to install.
get_unique_traders_by_collection 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_unique_traders_by_collection 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_unique_traders_by_collection. 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_unique_traders_by_collection is provided by the Nft Analytics MCP server (kukapay/nft-analytics-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 →