Get your puzzle storm dashboard
AI agents call get_puzzle_storm_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 dashboard information about puzzle storm performance. It queries existing data without creating, modifying, deleting, or executing external operations. The action is read-only with no side effects, fitting the Read category. Severity is low because accessing one's own dashboard poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get your puzzle storm dashboard' — a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get your puzzle storm dashboard. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_puzzle_storm_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_storm_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_storm_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_storm_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_storm_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_storm_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 →