accept_challenge · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What accept_challenge does on Lichess Integration

AI agents use accept_challenge 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
`challengeId`	string	—	ID of the challenge to accept

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why accept_challenge needs a policy

Accepting a challenge creates a new game on the platform, which is a reversible write action (the game can be aborted). It modifies state by initiating a game session, but does not delete data or execute arbitrary code.

From the tool's definition Accept an incoming challenge

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

accept_challenge Rate-limited

accept_challenge 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": {
    "accept_challenge": {
      "limits": [
        {
          "counter": "accept_challenge_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 accept_challenge

What does the accept_challenge tool do? +

Accept an incoming challenge. 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 accept_challenge accept? +

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

How do I enforce a policy on accept_challenge? +

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

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

Can I rate-limit accept_challenge? +

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

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

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