Get today
AI agents call lichess_get_daily_puzzle 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 fetches data (a daily puzzle) without creating, modifying, deleting, or executing arbitrary operations. It is a straightforward read operation with no side effects. The incomplete description ('Get today') is minimal but the tool name itself clearly indicates data retrieval. Severity is low because misuse causes no harm beyond potentially wasting API quota.
From the tool's definition Tool name 'lichess_get_daily_puzzle' and description 'Get today' indicate retrieval of puzzle data. The server context describes 'solving puzzles' as a read operation analogous to 'accessing user profiles and game history' which are non-mutating queries.
Attacks that exploit this kind of access
Get today. 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_daily_puzzle: 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_daily_puzzle 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_daily_puzzle 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_daily_puzzle. 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_daily_puzzle 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 →