Get your puzzle dashboard
AI agents call get_puzzle_dashboard 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 |
|---|---|---|---|
days | number | — | How many days of history to return (max 30) |
Parameters from the server's own tool schema.
This tool retrieves user puzzle statistics and dashboard information from Lichess. It has no capability to modify, delete, or execute operations. The read-only retrieval of personal puzzle data poses minimal security risk, as it only exposes information the authenticated user already has access to.
From the tool's definition Tool description states 'Get your puzzle dashboard' - a retrieval operation with no side effects. The verb 'get' and the passive data retrieval nature indicate this is a read-only operation that queries existing puzzle data without modification.
Attacks that exploit this kind of access
Get your puzzle dashboard. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_puzzle_dashboard accepts 1 parameter: days. 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_puzzle_dashboard: 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_puzzle_dashboard 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_puzzle_dashboard 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_puzzle_dashboard. 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_puzzle_dashboard 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 →