List saved Path of Building (PoE2) builds from the local filesystem. Searches for .xml build files in the default PoB2 Builds directory: - Windows: Documents/Path of Building (PoE2)/Builds/ (priority) or %APPDATA%/... - macOS: ~/Library/Application Support/Path of Building (PoE2)/Builds/ - Linux:...
AI agents call poe2_pob_local_builds 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 files from the local filesystem, specifically searching for .xml build files in user directories. It only lists/retrieves data without modifying anything. The medium severity reflects that it accesses the local filesystem and could expose directory structure and personal build data, but it's limited to a specific application's build files.
From the tool's definition List saved Path of Building (PoE2) builds from the local filesystem. Searches for .xml build files in the default PoB2 Builds directory.
Attacks that exploit this kind of access
List saved Path of Building (PoE2) builds from the local filesystem. Searches for .xml build files in the default PoB2 Builds directory: - Windows: Documents/Path of Building (PoE2)/Builds/ (priority) or %APPDATA%/... - macOS: ~/Library/Application Support/Path of Building (PoE2)/Builds/ - Linux: ~/.config/Path of Building (PoE2)/Builds/ Returns: List of build files with class, ascendancy, level, and last modified date. Note: If a custom path was provided via --pob2-path CLI flag, that path is used instead. Examples: -. 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_local_builds: 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_local_builds 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_local_builds 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_local_builds. 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_local_builds 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 →