Create a new Swiss tournament
AI agents use create_swiss to create or update resources in Lichess Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess Integration environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Name of the tournament |
clock | object | — | Clock settings |
rated | boolean | — | Whether the tournament is rated |
teamId | string | — | ID of the team hosting the tournament |
variant | string | — | Variant key |
nbRounds | number | — | Number of rounds to play |
description | string | — | Tournament description (HTML) |
roundInterval | number | — | Interval between rounds in seconds |
Parameters from the server's own tool schema.
This tool creates tournament data that can be persisted and made available to other users. While creation is reversible (tournaments can typically be deleted or archived), it modifies platform state and could be misused to create unwanted tournaments, spam the platform, or consume resources. However, it does not delete data (ruling out Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition 'Create a new Swiss tournament' - the tool creates a new tournament structure, which is a persistent data modification on the Lichess platform.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Create a new Swiss tournament. It is categorised as a Write tool in the Lichess Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_swiss accepts 8 parameters: name, clock, rated, teamId, variant, nbRounds, description, roundInterval. 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 create_swiss: 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.
create_swiss is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_swiss 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 create_swiss. 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.
create_swiss 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 →