Send a chat message in an active Lichess chess game, to the player or spectator chat room.
AI agents use lichess_send_chat to create or update resources in Lichess MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess MCP environment.
This tool creates new data (chat messages) in a reversible manner. Messages can typically be deleted, edited, or ignored. There is no code execution, data deletion, or financial impact. The blast radius is minimal — an AI sending unwanted or inappropriate chat messages would be a minor annoyance rather than a security risk, and the chat is scoped to an active game.
From the tool's definition Tool name 'lichess_send_chat' and description states it 'Send a chat message in an active Lichess chess game' — this creates/writes a new message that is visible to other players/spectators.
Attacks that exploit this kind of access
Send a chat message in an active Lichess chess game, to the player or spectator chat room. It is categorised as a Write tool in the Lichess MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_send_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 MCP. Nothing to install.
lichess_send_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 lichess_send_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 lichess_send_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.
lichess_send_chat is provided by the Lichess MCP server (jamespdaily/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 →