Get the Lichess leaderboard — top players by rating for a specific time control (bullet, blitz, rapid, classical, chess960, etc.).
AI agents call lichess_get_leaderboard to retrieve information from Lichess MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that fetches publicly available ranking information. There is no capability to modify user data, execute commands, delete records, or trigger financial transactions. The blast radius of misuse is minimal — an AI agent could at worst retrieve leaderboard data repeatedly, which has no harmful consequence.
From the tool's definition The tool 'lichess_get_leaderboard' retrieves and queries public leaderboard data for top players by rating across various time controls. The description explicitly indicates it 'Get[s]' data with no mention of modifications, deletions, or side effects.
Attacks that exploit this kind of access
Get the Lichess leaderboard — top players by rating for a specific time control (bullet, blitz, rapid, classical, chess960, etc.). It is categorised as a Read tool in the Lichess MCP MCP Server, which means it retrieves data without modifying state.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_get_leaderboard: 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 Lichess MCP. Nothing to install.
lichess_get_leaderboard 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 lichess_get_leaderboard 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 lichess_get_leaderboard. 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.
lichess_get_leaderboard is provided by the Lichess MCP server (jamespdaily/lichess-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 →