Set kid mode status
AI agents use set_kid_mode to create or update resources in Lichess Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess Integration environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
value | boolean | — | Enable or disable kid mode |
Parameters from the server's own tool schema.
The tool updates account state (kid mode status) but does not delete data, execute arbitrary code, move money, or perform irreversible actions. It's a reversible configuration change typical of Write category. Severity is low because changing kid mode status has minimal blast radius—it affects only content filtering and safety settings for the account holder, with no financial or destructive implications.
From the tool's definition Tool description states 'Set kid mode status' which modifies a user account setting. This is a write operation that changes account configuration on the Lichess platform.
Attacks that exploit this kind of access
Set kid mode status. It is categorised as a Write tool in the Lichess Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_kid_mode accepts 1 parameter: value. 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 set_kid_mode: 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.
set_kid_mode 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 set_kid_mode 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 set_kid_mode. 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.
set_kid_mode 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 →