Get rating history of a user for all perf types
AI agents call get_rating_history 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 |
|---|---|---|---|
username | string | — | Username of the player |
Parameters from the server's own tool schema.
The tool retrieves historical rating data for a user, which is a read-only operation. It does not create, modify, delete, or execute any actions. The data retrieved is typically public or user-accessible information on the Lichess platform. There is no capability to alter state, trigger external operations, or cause irreversible changes.
From the tool's definition Tool name 'get_rating_history' and description 'Get rating history of a user for all perf types' indicate data retrieval with no modifications or side effects. This is a straightforward query operation.
Attacks that exploit this kind of access
Get rating history of a user for all perf types. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_rating_history accepts 1 parameter: username. 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_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 Integration. Nothing to install.
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 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 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.
get_rating_history 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 →