This record as markdown: /tools/creativelead-unclick/lichess-user-games.md
What lichess_user_games does on UnClick
AI agents call lichess_user_games 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 |
|---|---|---|---|
max | number | — | |
api_key | string | — | |
perfType | string | — | |
username | string | — |
Parameters from the server's own tool schema.
Why lichess_user_games is rated Low
This tool retrieves historical game information from Lichess (a chess platform), which is a read-only operation with no side effects. It queries and returns data without altering it, creating financial obligations, or executing arbitrary operations. The blast radius is minimal—at worst, the AI agent could retrieve games for unintended users, but this causes no lasting harm given the data is public and immutable.
From the tool's definition Tool name 'lichess_user_games' and description 'Get games for a Lichess user' indicate retrieval of publicly available game data with no modification, deletion, or execution of code.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs lichess_user_games 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_games, this is the rule to start with:
lichess_user_games 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_games call is checked against it from then on.
Questions about lichess_user_games
Get games for a Lichess user. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lichess_user_games accepts 4 parameters: max, api_key, perfType, 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_games: 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_games 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_games 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_games. 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_games 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