Create a new simul
AI agents use create_simul 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 simul |
text | string | — | Description of the simul |
color | string | — | Color the host will play |
variant | string | — | Variant key |
clockTime | number | — | Clock initial time in minutes |
maxRating | number | — | Maximum rating to join |
minRating | number | — | Minimum rating to join |
clockIncrement | number | — | Clock increment in seconds |
Parameters from the server's own tool schema.
This tool creates a new simul event, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or trigger destructive changes. The blast radius is low—a misused simul creation would merely add an unwanted event to a user's account, easily deletable or ignorable by other users.
From the tool's definition Tool name 'create_simul' and description 'Create a new simul' indicate creation of a new resource (simul = simultaneous chess exhibition) on the Lichess platform.
Attacks that exploit this kind of access
Create a new simul. 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_simul accepts 8 parameters: name, text, color, variant, clockTime, maxRating, minRating, clockIncrement. 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_simul: 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_simul 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_simul 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_simul. 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_simul 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 →