This record as markdown: /tools/creativelead-unclick/lichess-user.md
What lichess_user does on UnClick
AI agents call lichess_user to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
username | string | — |
Parameters from the server's own tool schema.
Why lichess_user is rated Low
This tool retrieves user profile information from Lichess, a public chess platform. It performs a GET-like operation to fetch data, has no destructive or side effects, and does not execute code or move money. The low severity reflects that user profiles are typically public information with minimal blast radius if accessed by an AI agent.
From the tool's definition The tool is described as 'Get a Lichess user profile,' which is a retrieval operation that queries publicly available profile data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs lichess_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lichess_user, this is the rule to start with:
lichess_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every lichess_user call is checked against it from then on.
Questions about lichess_user
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. 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 (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue