AI agents call get_player_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 queries existing public player data from FACEIT without creating, modifying, deleting, or executing any operations. It has no side effects and presents no risk of data loss, code execution, or financial impact. The low severity reflects minimal harm even if misused—an agent could only retrieve statistics that are publicly available.
From the tool's definition Tool returns player statistics (ELO, skill level, region, lifetime stats) with no modification capability. The verb 'Return' and the nature of the data being queried (public FACEIT player stats) indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Return ELO, skill level, region, and lifetime CS2 stats 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_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_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_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_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_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 →