AI agents call lichess_user to retrieve information from UnClick 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 | Yes |
Parameters from the server's own tool schema.
This tool queries and returns user profile data from Lichess (a chess platform) without modifying, deleting, or executing any actions. It is a straightforward read operation that retrieves existing data. The blast radius of misuse is minimal—an attacker could enumerate user profiles but cannot cause financial harm, data loss, or execute arbitrary code.
From the tool's definition Tool description states 'Get a Lichess user profile', which is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a Lichess user profile. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lichess_user accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for lichess_user: 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 UnClick. Nothing to install.
lichess_user 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_user 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_user. 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_user is provided by the UnClick MCP server (@unclick/mcp-server). 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 →