AI agents call list_division_players 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 is a query/retrieval tool that aggregates player roster and profile information across a season and division hierarchy. While it is a 'power tool' that handles multiple API calls internally, it performs no mutations, destructive actions, code execution, or financial transactions. The blast radius of misuse is minimal—an agent could only retrieve competitive TF2 player data that is already public on RGL.gg.
From the tool's definition Tool retrieves roster and profile data for players in a division without modifying, deleting, or executing operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Power tool: every unique player who was rostered in (season, division), with optional bulk profile data. Handles the full Season→Group→Rosters→Profiles chain in one call. 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 list_division_players: 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.
list_division_players 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 list_division_players 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 list_division_players. 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.
list_division_players 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 →