List top WAX NFT collections sorted by asset count
AI agents call wax_list_collections to retrieve information from WAX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available WAX blockchain NFT collection information sorted by a metric (asset count). It performs no writes, deletions, code execution, or financial transactions. The operation is purely informational and read-only, presenting minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'wax_list_collections' combined with description 'List top WAX NFT collections sorted by asset count' indicates a query operation that retrieves and sorts data without modification or side effects.
Attacks that exploit this kind of access
List top WAX NFT collections sorted by asset count. It is categorised as a Read tool in the WAX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WAX MCP Server MCP server in PolicyLayer and add a rule for wax_list_collections: 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 WAX MCP Server. Nothing to install.
wax_list_collections 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 wax_list_collections 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 wax_list_collections. 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.
wax_list_collections is provided by the WAX MCP Server MCP server (yksanjo/wax-mcp-server). 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 →