Get a user's Lichess profile information
AI agents call get_user_profile 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 |
|---|---|---|---|
trophies | boolean | — | Include user trophies |
username | string | — | Username of the player |
Parameters from the server's own tool schema.
This tool retrieves profile information from Lichess—a standard GET/fetch operation. It has no capacity to modify data, execute operations, or cause harmful side effects. The blast radius of misuse is minimal; an agent could at most retrieve publicly available user information. Classification as Read is appropriate.
From the tool's definition Tool name 'get_user_profile' and description 'Get a user's Lichess profile information' indicate a read-only query operation that retrieves user data without modification or side effects.
Attacks that exploit this kind of access
Get a user's Lichess profile information. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_user_profile accepts 2 parameters: trophies, 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →