Write in the chat of a board game
AI agents use write_in_chat 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 |
|---|---|---|---|
room | string | — | The chat room |
text | string | — | The message to send |
gameId | string | — | The game ID |
Parameters from the server's own tool schema.
This tool creates new data (chat messages) reversibly without destructive or irreversible effects. Messages can be edited or deleted. It has no financial impact, does not execute arbitrary code, and fits the Write category for content creation. Severity is low because chat messages in a gaming context pose minimal risk—they are user-generated communications with limited blast radius even if an AI agent misuses them.
From the tool's definition Tool name 'write_in_chat' and description 'Write in the chat of a board game' explicitly indicate creating/posting chat messages within an existing game context.
Attacks that exploit this kind of access
Write in the chat of 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.
write_in_chat accepts 3 parameters: room, text, 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 write_in_chat: 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.
write_in_chat 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 write_in_chat 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 write_in_chat. 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.
write_in_chat 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 →