AI agents call search_axies to retrieve information from Axie without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data from the Axie Infinity marketplace. It performs a search operation with optional filters to return matching results. There is no indication that it modifies, deletes, executes code, or involves financial transactions—it purely reads and returns existing marketplace data.
From the tool's definition Tool description states 'Search for Axies on the marketplace' with filtering capabilities. The word 'search' and the filtering parameters (class, parts, breed count, auction type, owner) indicate a query operation that retrieves marketplace data without…
Attacks that exploit this kind of access
Search for Axies on the marketplace with optional filters. Supports filtering by class, parts, breed count, auction type, and owner. It is categorised as a Read tool in the Axie MCP Server, which means it retrieves data without modifying state.
Register the Axie MCP server in PolicyLayer and add a rule for search_axies: 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 Axie. Nothing to install.
search_axies 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 search_axies 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 search_axies. 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.
search_axies is provided by the Axie MCP server (jackdlogan/axie-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 →