AI agents call list_season_divisions 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 retrieves and lists existing divisions within a specified season. It queries data without creating, modifying, deleting, or executing any operations. No financial, destructive, or execute-class actions are possible. This is a straightforward Read operation with minimal risk if misused by an agent.
From the tool's definition Tool name 'list_season_divisions' and description 'List the divisions (groups) in a season' indicate a retrieval operation with no side effects. Consistent with sibling tools like 'list_division_players', 'find_division', 'find_season' etc.
Attacks that exploit this kind of access
List the divisions (groups) in a season. Pass a season phrase like. 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_season_divisions: 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_season_divisions 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_season_divisions 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_season_divisions. 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_season_divisions 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 →