Upgrade to Bot account. WARNING: This is irreversible and the account must not have played any games.
AI agents call upgrade_to_bot 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.
This tool performs an irreversible account conversion that fundamentally alters the account type and cannot be reverted. Even though it doesn't delete data, the permanent nature of the transformation and explicit warning about irreversibility place it in the Destructive category. The high severity reflects that an AI agent misusing this could permanently convert a user's account without recovery options.
From the tool's definition Tool description explicitly states 'WARNING: This is irreversible' and 'the account must not have played any games', indicating a permanent, one-way transformation of account state that cannot be undone.
Attacks that exploit this kind of access
Upgrade to Bot account. WARNING: This is irreversible and the account must not have played any games. 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.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for upgrade_to_bot: 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.
upgrade_to_bot 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 upgrade_to_bot 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 upgrade_to_bot. 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.
upgrade_to_bot 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 →