Critical Risk →

upgrade_to_bot

Upgrade to Bot account. WARNING: This is irreversible and the account must not have played any games.

Part of the Lichess Integration MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

karayaman/lichess-mcp Destructive

AI agents may call upgrade_to_bot to permanently remove or destroy resources in Lichess Integration. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call upgrade_to_bot in a loop, permanently destroying resources in Lichess Integration. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

karayaman-lichess-mcp.yaml
tools:
  upgrade_to_bot:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Lichess Integration policy for all 88 tools.

Tool Name upgrade_to_bot
Category Destructive
Risk Level Critical

View all 88 tools →

Agents calling destructive-class tools like upgrade_to_bot have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

upgrade_to_bot is one of the critical-risk operations in Lichess Integration. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the upgrade_to_bot tool do? +

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.

How do I enforce a policy on upgrade_to_bot? +

Add a rule in your Intercept YAML policy under the tools section for upgrade_to_bot. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lichess Integration MCP server.

What risk level is upgrade_to_bot? +

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.

Can I rate-limit upgrade_to_bot? +

Yes. Add a rate_limit block to the upgrade_to_bot rule in your Intercept 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 upgrade_to_bot completely? +

Set action: deny in the Intercept 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.

What MCP server provides upgrade_to_bot? +

upgrade_to_bot is provided by the Lichess Integration MCP server (karayaman/lichess-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.