Decline an incoming chess challenge on Lichess. Optionally provide a reason.
AI agents use lichess_decline_challenge to create or update resources in Lichess MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess MCP environment.
Declining a challenge modifies the state of a pending challenge (from open to declined), which is a reversible/transactional write action. It does not delete data permanently, execute code, or involve finances. The blast radius is minimal — worst case is a missed game opportunity.
From the tool's definition Decline an incoming chess challenge on Lichess. Optionally provide a reason.
Attacks that exploit this kind of access
Decline an incoming chess challenge on Lichess. Optionally provide a reason. It is categorised as a Write tool in the Lichess MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_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 MCP. Nothing to install.
lichess_decline_challenge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lichess_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.
Set action: deny in the PolicyLayer policy for lichess_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.
lichess_decline_challenge is provided by the Lichess MCP server (jamespdaily/lichess-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →