Look up detailed game data from poe2db.tw — items, gems, mods, passives. poe2db.tw contains datamined information directly from game files, including exact stat values, gem scaling, mod tiers, and more. Useful for finding translations of game terms in various languages. IMPORTANT: Skills, passive...
AI agents call poe2_db_lookup to retrieve information from Poe2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against a public game database API. It retrieves and returns static game data (items, gems, mods, passives, stat values) with no side effects, no data modification, no code execution, and no financial impact. The instruction about Roman numeral conversion is purely presentational formatting for the user. This is a straightforward information lookup utility with minimal risk.
From the tool's definition Tool description states: 'Look up detailed game data' and 'retrieve datamined game information from public APIs.' The sibling tools include currency prices, item prices, and meta-build statistics—all read operations.
Attacks that exploit this kind of access
Look up detailed game data from poe2db.tw — items, gems, mods, passives. poe2db.tw contains datamined information directly from game files, including exact stat values, gem scaling, mod tiers, and more. Useful for finding translations of game terms in various languages. IMPORTANT: Skills, passives, and ascendancy nodes with ranks use Roman numerals in poe2db, not Arabic. Convert rank numbers: 1→I, 2→II, 3→III, 4→IV, 5→V. Always include the rank suffix if the user mentions a specific rank. Args: - term (string): English name of an item, gem, mod, etc. Use underscores for spaces, e.g. It is categorised as a Read tool in the Poe2 MCP Server, which means it retrieves data without modifying state.
Register the Poe2 MCP server in PolicyLayer and add a rule for poe2_db_lookup: 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 Poe2. Nothing to install.
poe2_db_lookup 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 poe2_db_lookup 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 poe2_db_lookup. 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.
poe2_db_lookup is provided by the Poe2 MCP server (sergeyklay/poe2-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 →