Resign a board game
AI agents use resign_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 |
|---|---|---|---|
gameId | string | — | The game ID |
Parameters from the server's own tool schema.
Resigning a game is a reversible write action in the sense that it modifies game state (concedes the game), but it does not delete data. While the resignation cannot be undone, it is a standard game action rather than data destruction — the game record remains intact. It has a medium severity since it terminates an ongoing game on behalf of the user.
From the tool's definition Resign a board game
Attacks that exploit this kind of access
Resign 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.
resign_board_game accepts 1 parameter: 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 resign_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.
resign_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 resign_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 resign_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.
resign_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 →