list_equipment
AI agents call list_equipment 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.
The 'list_' prefix strongly suggests enumeration/retrieval of equipment data from the game files without modification, deletion, or execution capabilities. No side effects are possible with a listing operation. The empty description lowers confidence slightly, but the naming convention and server context (providing read-only game data access) make classification as Read appropriate.
From the tool's definition Tool name 'list_equipment' with 'list' verb indicates data retrieval operation. Context shows server provides game data parsing (tank statistics, armor values, equipment, camouflages) with sibling tools like 'list_camouflages' and 'list_consumables' following…
Attacks that exploit this kind of access
list_equipment. 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 list_equipment: 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.
list_equipment 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 list_equipment 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 list_equipment. 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.
list_equipment 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 →