AI agents call find_division 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 or resolves division information from the RGL.gg API without modifying data or triggering external operations. It follows a standard Read pattern alongside other data-retrieval tools in the same server. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'find_division' and sibling tools with 'find_', 'get_', and 'list_' prefixes indicate query/lookup operations.
Attacks that exploit this kind of access
Resolve a division name 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 find_division: 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_division 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_division 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_division. 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_division 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 →