AI agents call get_player_map_stats to retrieve information from Faceit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns statistical information about a player's performance across different maps in CS2. It performs a read-only query against public FACEIT data with no capability to modify, delete, or execute arbitrary operations. The worst-case misuse would be information gathering about a player, which carries minimal risk. No financial, destructive, or code execution capabilities are present.
From the tool's definition Tool name 'get_player_map_stats' and description 'Return per-map performance breakdown for a FACEIT player' indicate data retrieval with no modification or side effects. The server is explicitly described as querying public FACEIT player data.
Attacks that exploit this kind of access
Return per-map performance breakdown for a FACEIT player. It is categorised as a Read tool in the Faceit MCP Server, which means it retrieves data without modifying state.
Register the Faceit MCP server in PolicyLayer and add a rule for get_player_map_stats: 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 Faceit. Nothing to install.
get_player_map_stats 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 get_player_map_stats 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 get_player_map_stats. 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.
get_player_map_stats is provided by the Faceit MCP server (tqakdev/faceit-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 →