Cancel an outgoing chess challenge you sent on Lichess.
AI agents call lichess_cancel_challenge to permanently remove resources in Lichess MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling a challenge irreversibly withdraws the outgoing invitation — the challenged party can no longer accept it. This is a one-way action that cannot be undone (the original challenge state is gone). However, the blast radius is very low: only a single pending game invitation is affected, with no financial, data-loss, or system consequences.
From the tool's definition Cancel an outgoing chess challenge you sent on Lichess
Attacks that exploit this kind of access
Cancel an outgoing chess challenge you sent on Lichess. It is categorised as a Destructive tool in the Lichess MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_cancel_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_cancel_challenge is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the lichess_cancel_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_cancel_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_cancel_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 →