lichess.players.top
Top N players in a chess variant (bullet, blitz, rapid, classical, ultraBullet, chess960, crazyhouse, antichess, atomic, horde, kingOfTheHill, racingKings, threeCheck). Returns username, rating, country.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/lichess.players.top.md
What lichess.players.top does on Apibase
AI agents call lichess.players.top to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
nb | integer | — | Number of top players to return (1–200). Defaults to 10. |
perf_type | string | Yes | Chess variant to rank players by. One of: bullet, blitz, rapid, classical, ultraBullet, chess960, crazyhouse, antichess, atomic, horde, kingOfTheHill, racingKin |
Parameters from the server's own tool schema.
Why lichess.players.top is rated Low
Queries public leaderboard data without creating, modifying, or deleting any resources.
From the tool's definition Returns username, rating, country. No modification or side effects.
Attacks that exploit this kind of access
The rule that runs lichess.players.top safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lichess.players.top, this is the rule to start with:
lichess.players.top is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every lichess.players.top call is checked against it from then on.
Questions about lichess.players.top
Top N players in a chess variant (bullet, blitz, rapid, classical, ultraBullet, chess960, crazyhouse, antichess, atomic, horde, kingOfTheHill, racingKings, threeCheck). Returns username, rating, country. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
lichess.players.top accepts 2 parameters: nb, perf_type. Required: perf_type. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for lichess.players.top: 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 Apibase. Nothing to install.
lichess.players.top 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.players.top 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.players.top. 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.players.top is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue