Export all chapters of a study in PGN format
AI agents call export_all_study_chapters 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 |
|---|---|---|---|
studyId | string | — | Study ID |
Parameters from the server's own tool schema.
This tool retrieves study chapter data in PGN format. It is a read/export operation with no side effects — it fetches existing data without modifying, deleting, or executing anything.
From the tool's definition Export all chapters of a study in PGN format
Attacks that exploit this kind of access
Export all chapters of a study in PGN format. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
export_all_study_chapters accepts 1 parameter: studyId. 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_all_study_chapters: 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_all_study_chapters 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_all_study_chapters 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_all_study_chapters. 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_all_study_chapters 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 →