This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/lichess-tournament.md
What lichess_tournament does on UnClick
AI agents call lichess_tournament 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 |
|---|---|---|---|
tournament_id | string | Yes |
Parameters from the server's own tool schema.
Why lichess_tournament is rated Low
This tool retrieves tournament information from Lichess (a chess platform). It performs a read-only query operation that returns data without modifying, executing, deleting, or causing financial transactions. The blast radius of misuse is minimal—an agent could only retrieve publicly available tournament data.
From the tool's definition Tool name 'lichess_tournament' and description 'Get details for a Lichess tournament' indicate a retrieval operation. The verb 'Get' and noun 'details' are consistent with query/fetch semantics with no side effects.
Attacks that exploit this kind of access
The rule that runs lichess_tournament 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_tournament, this is the rule to start with:
lichess_tournament 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_tournament call is checked against it from then on.
Questions about lichess_tournament
Get details for a Lichess tournament. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
lichess_tournament accepts 1 parameter: tournament_id. Required: tournament_id. 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_tournament: 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_tournament 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_tournament 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_tournament. 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_tournament 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue