// SCAN REPORT

Rgl

14 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 3 Jul 2026

0 can modify or destroy data

14 read-only

14 tools total

Community server · catalogue entry verified 03/07/2026

How to control Rgl ↓

TOOL MAP

What Rgl exposes to your agents

Read (14) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Rgl

PolicyLayer is an MCP gateway — it sits between your AI agents and Rgl, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "find_division": {
    "limits": [
      {
        "counter": "find_division_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rgl — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON RGL →

Instant setup, no code required.

FULL CATALOGUE

All 14 Rgl tools

READ 14 tools

Read find_division Resolve a division name like Read find_player Search player aliases (contains-match). Returns SteamIds you can pass to get_player. Read find_region Resolve a region phrase like Read find_season Resolve a free-form season name like Read find_team Search teams by name or tag (contains-match). Returns SteamIds for the team rows. Optionally narrow by season Read get_match Fetch a single match by MatchId (teams, maps, scores, winner). Read get_player Fetch a player profile by SteamID (current alias, avatar, ban info, active team per format). Read get_season Reverse lookup: resolve an internal SeasonId (e.g. the Read get_team Fetch full team data by TeamId (roster, season, division, linked teams, match IDs). Read list_division_players Power tool: every unique player who was rostered in (season, division), with optional bulk profile data. Handl Read list_division_teams List all teams in (season, division). Excludes the Read list_formats List all formats (cached). Useful for the model to discover what formats exist before mapping a phrase. Read list_regions List all regions (cached). Useful when a region phrase doesn Read list_season_divisions List the divisions (groups) in a season. Pass a season phrase like

FAQ

Questions about Rgl

Is the Rgl MCP server safe to use without restrictions? +

The Rgl server is primarily read-only with 14 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Rgl MCP server expose? +

14 tools across 1 categories: Read. 14 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Rgl? +

Register the Rgl MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rgl tool call.

Deterministic rules across all 14 Rgl tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RGL →

Instant setup, no code required.

14 Rgl tools catalogued and risk-classified — across an index of 43,000+ MCP servers.