Get the leaderboard for a single speed or variant
AI agents call get_leaderboard to retrieve information from Lichess Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
nb | number | — | How many users to fetch (1-200) |
perfType | string | — | The speed or variant |
Parameters from the server's own tool schema.
This tool retrieves and queries leaderboard information from the Lichess platform. It is a read-only operation that does not create, modify, delete, or execute any changes. Public leaderboard data has minimal sensitivity and poses no risk of unauthorized data manipulation or destructive actions. The blast radius of misuse is negligible.
From the tool's definition Tool name 'get_leaderboard' and description 'Get the leaderboard for a single speed or variant' indicate retrieval of public ranking data with no modification or side effects.
Attacks that exploit this kind of access
Get the leaderboard for a single speed or variant. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_leaderboard accepts 2 parameters: nb, perfType. The full parameter table on this page comes from the server's own tool schema.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for 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 Integration. Nothing to install.
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 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 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.
get_leaderboard is provided by the Lichess Integration MCP server (karayaman/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 →