Play a chess move in an active Lichess game using UCI notation (e.g. e2e4, d7d5, e7e8q for promotion). Submit your move during a live game.
AI agents invoke lichess_make_move to trigger actions in Lichess MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation on the Lichess platform by submitting a move in a live game. It is not merely writing data locally — it interacts with an ongoing real-time game session, affecting game state for both players. This fits the Execute category (triggers external operations whose effects depend on arguments).
From the tool's definition 'Play a chess move in an active Lichess game', 'Submit your move during a live game'
Attacks that exploit this kind of access
Play a chess move in an active Lichess game using UCI notation (e.g. e2e4, d7d5, e7e8q for promotion). Submit your move during a live game. It is categorised as a Execute tool in the Lichess MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_make_move: 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_make_move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lichess_make_move 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_make_move. 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_make_move 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 →