AI agents call get_axie_children 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 retrieves and returns parentage and breeding history information for an Axie NFT. It is a passive data query operation with no capability to modify game state, execute code, delete data, or move funds. The action is purely informational, consistent with other Read tools on the server like get_axie, get_land, and get_leaderboard.
From the tool's definition Tool name 'get_axie_children' and description 'Get the children (bred Axies) and parentage information for a given Axie' indicate a retrieval operation that queries existing game data without modifying, executing operations, or causing side effects.
Attacks that exploit this kind of access
Get the children (bred Axies) and parentage information for a given Axie. 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 get_axie_children: 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.
get_axie_children 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_axie_children 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_axie_children. 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_axie_children 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 →