AI agents call find_player to retrieve information from Rgl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple search/lookup operation to find player aliases and return their SteamIds. It retrieves information from the RGL.gg API without modifying, deleting, or executing any operations. This is a classic Read operation—low severity since it only queries publicly available competitive gaming data with no blast radius if misused.
From the tool's definition Tool description states it 'Search player aliases' and 'Returns SteamIds you can pass to get_player'. The verb 'search' and the fact it only retrieves and returns identifiers indicates a read-only query operation with no data modification or side effects.
Attacks that exploit this kind of access
Search player aliases (contains-match). Returns SteamIds you can pass to get_player. It is categorised as a Read tool in the Rgl MCP Server, which means it retrieves data without modifying state.
Register the Rgl MCP server in PolicyLayer and add a rule for find_player: 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 Rgl. Nothing to install.
find_player 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 find_player 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 find_player. 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.
find_player is provided by the Rgl MCP server (rglgg/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
find_player is one line of Rgl'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 →