make_move · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What make_move does on Lichess Integration

AI agents invoke make_move to trigger actions in Lichess Integration. 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.

PARAMETERS

Parameter	Type	Required	Description
`move`	string	—	Move in UCI format (e.g. 'e2e4')
`gameId`	string	—	ID of the game
`offeringDraw`	boolean	—	Whether to offer/accept a draw

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why make_move needs a policy

Making a move is an external action that alters the state of an ongoing game on the Lichess platform. It is not merely reading data, nor does it delete or involve finances. It executes a game action whose effect depends on the argument (the move). Misuse could cause an AI agent to make unintended or game-losing moves on behalf of the user, with high impact on active games.

From the tool's definition "Make a move in an ongoing game" — triggers an external operation on the Lichess platform that changes the state of a live chess game

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

make_move Rate-limited

make_move stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "make_move": {
      "limits": [
        {
          "counter": "make_move_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lichess Integration, so you can run agents against it safely.

FAQ

Questions about make_move

What does the make_move tool do? +

Make a move in an ongoing game. It is categorised as a Execute tool in the Lichess Integration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does make_move accept? +

make_move accepts 3 parameters: move, gameId, offeringDraw. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on make_move? +

Register the Lichess Integration MCP server in PolicyLayer and add a rule for 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 Integration. Nothing to install.

What risk level is make_move? +

make_move is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit make_move? +

Yes. Add a rate_limit block to the 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.

How do I block make_move completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides make_move? +

make_move 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.