set_token · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What set_token does on Lichess Integration

AI agents use set_token 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.

PARAMETERS

Parameter	Type	Required	Description
`token`	string	—	Your Lichess API token

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why set_token needs a policy

This tool creates or modifies API token configuration, which is a reversible write operation. However, severity is elevated to 'high' rather than 'medium' because misuse could compromise account security—an attacker could set a token to intercept future authentication or lock the legitimate user out.

From the tool's definition Tool name 'set_token' and description 'Set your Lichess API token' indicate the tool modifies stored authentication credentials.

Risk signalsHandles credentials or secrets (token)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_token Rate-limited

set_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_token": {
      "limits": [
        {
          "counter": "set_token_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_token

What does the set_token tool do? +

Set your Lichess API token. 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.

What parameters does set_token accept? +

set_token accepts 1 parameter: token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_token? +

Register the Lichess Integration MCP server in PolicyLayer and add a rule for set_token: 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 set_token? +

set_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_token? +

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

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

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