AI agents call get_erc1155_tokens 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 is a straightforward data retrieval tool that queries blockchain token information. It retrieves game item data (runes, charms, accessories, etc.) without side effects. No creation, modification, deletion, code execution, or financial transactions are involved. The worst-case misuse would be information disclosure about in-game assets, which has minimal blast radius in a gaming context.
From the tool's definition Tool name 'get_erc1155_tokens' and description 'Get ERC1155 tokens' indicate a retrieval operation. The phrase 'optionally filtered by owner' confirms it queries or lists existing blockchain token data without modifying, creating, or deleting anything.
Attacks that exploit this kind of access
Get ERC1155 tokens such as runes, charms, accessories, ingredients, and other in-game items, optionally filtered by 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 get_erc1155_tokens: 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_erc1155_tokens 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_erc1155_tokens 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_erc1155_tokens. 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_erc1155_tokens 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 →