AI agents call get_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.
get_player retrieves player profile information from a competitive TF2 database using a SteamID lookup. No data is created, modified, deleted, or financial/code execution occurs. This is a straightforward data retrieval operation with read-only semantics and minimal blast radius if misused (at worst, an agent queries public competitive player profiles repeatedly).
From the tool's definition Tool description uses 'Fetch a player profile' which retrieves data (alias, avatar, ban info, team affiliation) with no modification or side effects.
Attacks that exploit this kind of access
Fetch a player profile by SteamID (current alias, avatar, ban info, active team per format). 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 get_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.
get_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 get_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 get_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.
get_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.
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 →