unblock_user · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What unblock_user does on Lichess Integration

AI agents use unblock_user 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
`username`	string	—	Username of the player to unblock

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why unblock_user needs a policy

Unblocking a user modifies account relationship state by reversing a block, which is a reversible write operation. It creates/restores a social relationship rather than deleting data irreversibly. Low severity as it only affects user interaction settings.

From the tool's definition Unblock a user

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unblock_user Rate-limited

unblock_user 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": {
    "unblock_user": {
      "limits": [
        {
          "counter": "unblock_user_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 unblock_user

What does the unblock_user tool do? +

Unblock a user. 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 unblock_user accept? +

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

How do I enforce a policy on unblock_user? +

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

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

Can I rate-limit unblock_user? +

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

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

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