AI agents call poe2_log_summary 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 reads and analyzes existing local log file data to extract game events for analysis. It performs no write, execute, destructive, or financial operations. The scope is limited to querying local game logs, making it a straightforward Read operation with low severity since misuse would only expose player event metadata without enabling unauthorized actions or data loss.
From the tool's definition Tool name and description indicate it 'Parse[s] the local PoE2 log file and return[s] game events' and 'Extracts raw player events, zone transitions, and session timing' — all read-only retrieval operations on local log data with no modification, deletion, or…
Attacks that exploit this kind of access
Parse the local PoE2 log file and return game events for analysis. Extracts raw player events, zone transitions, and session timing from the game. 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_log_summary: 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_log_summary 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_log_summary 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_log_summary. 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_log_summary 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 →