Get your ongoing games (real-time and correspondence)
AI agents call get_ongoing_games 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 | integer | — | Max number of games to fetch (1-50) |
Parameters from the server's own tool schema.
This is a read-only query operation that retrieves information about the user's active games from the Lichess platform. It has no capability to modify game state, delete data, execute code, or create financial obligations. The blast radius of misuse is minimal—an agent could only retrieve the user's own game information, which is already known to the authenticated user.
From the tool's definition Tool name 'get_ongoing_games' and description 'Get your ongoing games' clearly indicate data retrieval with no side effects. This fetches existing game state without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get your ongoing games (real-time and correspondence). It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_ongoing_games accepts 1 parameter: nb. 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_ongoing_games: 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_ongoing_games 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_ongoing_games 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_ongoing_games. 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_ongoing_games 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 →