Get your Lichess puzzle activity history — recent puzzles you attempted, results, ratings, and themes.
AI agents call lichess_get_puzzle_activity to retrieve information from Lichess MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to fetch user puzzle history and statistics. It has no side effects, does not modify any data, does not execute code or external operations, and does not involve financial transactions. It is a straightforward data retrieval endpoint typical of Read category tools.
From the tool's definition Tool retrieves 'your Lichess puzzle activity history — recent puzzles you attempted, results, ratings, and themes.' Uses 'get' verb and describes read-only retrieval of historical data with no modification, creation, or deletion.
Attacks that exploit this kind of access
Get your Lichess puzzle activity history — recent puzzles you attempted, results, ratings, and themes. It is categorised as a Read tool in the Lichess MCP MCP Server, which means it retrieves data without modifying state.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_get_puzzle_activity: 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 MCP. Nothing to install.
lichess_get_puzzle_activity 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 lichess_get_puzzle_activity 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 lichess_get_puzzle_activity. 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.
lichess_get_puzzle_activity is provided by the Lichess MCP server (jamespdaily/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 →