Get the chess rating history over time for a Lichess player across all time controls (bullet, blitz, rapid, classical, etc.).
AI agents call lichess_get_rating_history 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 queries and retrieves public user profile data (rating history across time controls). It has no capability to modify data, execute code, delete records, or perform financial operations. The information retrieved is historical and read-only. Low severity because misuse would only expose non-sensitive gaming statistics already publicly available on Lichess profiles.
From the tool's definition Tool name and description indicate it retrieves historical rating data: 'Get the chess rating history over time for a Lichess player'. Uses 'Get' verb and returns historical information without modification or side effects.
Attacks that exploit this kind of access
Get the chess rating history over time for a Lichess player across all time controls (bullet, blitz, rapid, classical, etc.). 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_rating_history: 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_rating_history 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_rating_history 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_rating_history. 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_rating_history 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 →