Get public data of a user
AI agents call get_user_public_data 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 |
withTrophies | boolean | — | Include user trophies |
Parameters from the server's own tool schema.
This tool retrieves user profile information that is already publicly accessible on the Lichess platform. It performs a query operation with no capability to modify, delete, or execute actions. The 'public' qualifier confirms the data is not sensitive or restricted. The blast radius of misuse is minimal since the information is non-sensitive and already available to the public.
From the tool's definition Tool name 'get_user_public_data' and description 'Get public data of a user' indicate retrieval of publicly available information without modification or side effects.
Attacks that exploit this kind of access
Get public data 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_public_data accepts 2 parameters: username, withTrophies. 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_public_data: 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_public_data 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_public_data 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_public_data. 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_public_data 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 →