detailed 1v1 breakdown
AI agents call analyze_matchup to retrieve information from WoT Blitz MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing game data (tank statistics, matchup analysis) from local game files. It performs no modifications, deletions, code execution, or financial operations. The analysis is a computed view over read data, which remains in the 'Read' category. The blast radius of misuse is minimal since it only returns informational game data.
From the tool's definition Tool name 'analyze_matchup' and description 'detailed 1v1 breakdown' indicate data retrieval and analysis of game statistics. The sibling tools (analyze_match, compare_tanks, get_tank, get_map) are all read operations that query game data without modification.
Attacks that exploit this kind of access
detailed 1v1 breakdown. It is categorised as a Read tool in the WoT Blitz MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WoT Blitz MCP Server MCP server in PolicyLayer and add a rule for analyze_matchup: 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 WoT Blitz MCP Server. Nothing to install.
analyze_matchup 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_matchup 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_matchup. 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_matchup is provided by the WoT Blitz MCP Server MCP server (revenant30102000/wotblitz-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 →