AI agents call poe2_pob_compare 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.
The tool retrieves and compares build information from Path of Building URLs but does not create, modify, delete, or execute any game operations or code. It is a passive analysis tool that returns comparison results. No financial transactions, irreversible changes, or command execution are involved. This fits the 'Read' category as it queries and retrieves data with no side effects.
From the tool's definition Tool compares two Path of Building 2 builds to identify differences. Accepts pobb.in URLs as input. This is purely a read/query operation that retrieves and analyzes existing build data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Compare two Path of Building 2 builds to identify differences. Accepts any combination of: - pobb.in URL (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_pob_compare: 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_pob_compare 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_pob_compare 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_pob_compare. 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_pob_compare 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 →