decline_challenge · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What decline_challenge does on Lichess Integration

AI agents use decline_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
`reason`	string	—	Reason for declining
`challengeId`	string	—	ID of the challenge to decline

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why decline_challenge needs a policy

Declining a challenge modifies the state of an incoming challenge (rejecting it), which is a reversible-class write action. It does not delete data, execute code, or involve financial transactions. The blast radius is low as it only affects a pending chess challenge.

From the tool's definition Decline an incoming challenge

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

decline_challenge Rate-limited

decline_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": {
    "decline_challenge": {
      "limits": [
        {
          "counter": "decline_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 decline_challenge

What does the decline_challenge tool do? +

Decline 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 decline_challenge accept? +

decline_challenge accepts 2 parameters: reason, challengeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on decline_challenge? +

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

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

Can I rate-limit decline_challenge? +

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

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

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