Get performance statistics of a user
AI agents call get_user_performance 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 |
|---|---|---|---|
perf | string | — | The speed or variant |
username | string | — | Username of the player |
Parameters from the server's own tool schema.
This tool queries and retrieves performance statistics from the Lichess platform without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no side effects, fitting the Read category. Severity is low since exposure of public user statistics poses minimal security risk.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get performance statistics of a user', indicating retrieval-only operation with no data modification or external state changes.
Attacks that exploit this kind of access
Get performance statistics of a user. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_user_performance accepts 2 parameters: perf, 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_user_performance: 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_user_performance 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_user_performance 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_user_performance. 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_user_performance 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 →