Create a new arena tournament
AI agents use create_arena 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 |
rated | boolean | — | Whether the tournament is rated |
hasChat | boolean | — | Whether players can discuss in a chat |
minutes | number | — | Tournament duration in minutes |
variant | string | — | Variant key |
position | string | — | Custom initial position in FEN format |
clockTime | number | — | Clock initial time in minutes |
startDate | number | — | Timestamp to start the tournament at a given date |
conditions | object | — | Restrict participation |
streakable | boolean | — | Whether players can get streaks |
berserkable | boolean | — | Whether players can use berserk |
description | string | — | Tournament description (HTML) |
Parameters from the server's own tool schema.
Creating an arena tournament is a write operation that generates new data (a tournament) in the Lichess system. The action is reversible (tournaments can be cancelled or deleted), has minimal blast radius, and requires no financial transaction or irreversible data destruction. This is a straightforward create/write operation on a game/competitive platform.
From the tool's definition Tool name 'create_arena' and description 'Create a new arena tournament' indicate the tool creates a new tournament resource.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
Create a new arena 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_arena accepts 12 parameters: name, rated, hasChat, minutes, variant, position, clockTime, startDate, conditions, streakable, berserkable, description. 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_arena: 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_arena 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_arena 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_arena. 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_arena 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 →