AI agents call analyze_dps_logs to retrieve information from DPSCoach without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and aggregates DPS metrics from existing combat logs stored in the local DuckDB event store. It performs analysis and returns a summary payload to the user, which is a read-only operation with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal — an agent could only retrieve game performance data already accessible within the local system.
From the tool's definition Tool description states it 'Return[s] the DPS summary payload for TL logs' — a retrieval operation that reads and summarizes existing combat log data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Return the DPS summary payload for TL logs. It is categorised as a Read tool in the DPSCoach MCP Server, which means it retrieves data without modifying state.
Register the DPSCoach MCP server in PolicyLayer and add a rule for analyze_dps_logs: 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 DPSCoach. Nothing to install.
analyze_dps_logs 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 analyze_dps_logs 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 analyze_dps_logs. 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.
analyze_dps_logs is provided by the DPSCoach MCP server (stalcup-dev/tl-dps-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 →