Cancel an outgoing challenge
AI agents call cancel_challenge to permanently remove resources in Lichess Integration — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
challengeId | string | — | ID of the challenge to cancel |
Parameters from the server's own tool schema.
Cancelling an outgoing challenge is an irreversible action that removes the challenge from the system. The other party can no longer accept it, and the action cannot be undone. This maps most closely to Destructive, as it permanently removes a previously created resource.
From the tool's definition Cancel an outgoing challenge
Attacks that exploit this kind of access
Cancel an outgoing challenge. It is categorised as a Destructive tool in the Lichess Integration MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_challenge accepts 1 parameter: challengeId. The full parameter table on this page comes from the server's own tool schema.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for 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 Integration. Nothing to install.
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 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 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.
cancel_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.
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 →