Create a puzzle race
AI agents use create_puzzle_race 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.
This tool creates a new puzzle race, which is a reversible modification to platform data. It falls squarely in the Write category—it adds data to the Lichess system but does not delete, execute external code, or move financial resources.
From the tool's definition The tool name 'create_puzzle_race' indicates it creates a new puzzle race entity on the Lichess platform. The description states 'Create a puzzle race,' which is an explicit create operation that modifies the platform state by adding a new resource.
Attacks that exploit this kind of access
Create a puzzle race. 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.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for create_puzzle_race: 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_puzzle_race 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_puzzle_race 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_puzzle_race. 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_puzzle_race 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 →