AI agents call get_axie_transfer_history 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 existing on-chain transaction history for an Axie NFT. It performs a read-only operation on publicly available blockchain data. No data is created, modified, deleted, or financial transactions are initiated. The blast radius of misuse is minimal, as an agent could only retrieve historical information already public on the blockchain.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get the on-chain transfer and sale history' — retrieves historical blockchain data without modification, side effects, or access to financial operations.
Attacks that exploit this kind of access
Get the on-chain transfer and sale history for a specific 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_transfer_history: 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_transfer_history 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_transfer_history 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_transfer_history. 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_transfer_history 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 →