Handle draw offers for a board game
AI agents use handle_draw_board_game 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 |
|---|---|---|---|
accept | boolean | — | Whether to accept or decline the draw offer |
gameId | string | — | The game ID |
Parameters from the server's own tool schema.
The tool performs a reversible modification to game state (accepting/declining a draw offer). It does not execute arbitrary code, delete data permanently, involve financial transactions, or run system commands. It falls squarely into the Write category. Severity is low because the impact is confined to a single chess game and can be undone by playing on or restarting.
From the tool's definition "Handle draw offers for a board game" — this tool accepts or declines a draw offer, which modifies the state of an ongoing game (draw agreement status) but is fully reversible within the game context.
Attacks that exploit this kind of access
Handle draw offers for a board game. 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.
handle_draw_board_game accepts 2 parameters: accept, gameId. 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 handle_draw_board_game: 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.
handle_draw_board_game 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 handle_draw_board_game 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 handle_draw_board_game. 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.
handle_draw_board_game 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 →