AI agents call get_elo_trend 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 queries and retrieves previously stored ELO snapshot data for a player—a passive read operation with no side effects. It fits the Read category definition of retrieving or querying data without side effects. Severity is low because ELO trends are public gaming statistics that pose minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_elo_trend' and description 'Return stored ELO snapshots for a registered FACEIT player' indicate retrieval of historical ELO data. No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
Return stored ELO snapshots for a registered 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_elo_trend: 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_elo_trend 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_elo_trend 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_elo_trend. 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_elo_trend 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.
get_elo_trend is one line of Faceit's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →