Export one game in PGN or JSON format
AI agents call export_game 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 |
|---|---|---|---|
tags | boolean | — | Include the PGN tags |
evals | boolean | — | Include analysis evaluation comments |
moves | boolean | — | Include the PGN moves |
clocks | boolean | — | Include clock comments in the PGN moves |
gameId | string | — | The game ID |
opening | boolean | — | Include opening name |
accuracy | boolean | — | Include accuracy percentages |
literate | boolean | — | Include textual annotations |
pgnInJson | boolean | — | Include the full PGN within the JSON response |
Parameters from the server's own tool schema.
This tool retrieves and exports game data in a standard format (PGN or JSON). It is a read-only operation with no side effects, modifications, or destructive actions. The blast radius if misused is minimal — it only exposes chess game data.
From the tool's definition Export one game in PGN or JSON format
Attacks that exploit this kind of access
Export one game in PGN or JSON format. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
export_game accepts 9 parameters: tags, evals, moves, clocks, gameId, opening, accuracy, literate, pgnInJson. 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 export_game: 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.
export_game 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 export_game 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 export_game. 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.
export_game 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 →