Add a private note about a user
AI agents use add_user_note 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 |
|---|---|---|---|
text | string | — | The contents of the note |
username | string | — | Username of the player |
Parameters from the server's own tool schema.
This tool creates or modifies user-specific metadata (a private note) without destructive, financial, or code-execution implications. It falls squarely into the Write category. Severity is low because the blast radius of misuse is minimal—unwanted notes about other users are annoying but easily corrected and have no systemic impact on the Lichess platform or financial consequences.
From the tool's definition Tool name 'add_user_note' and description 'Add a private note about a user' indicate data creation/modification. The action is reversible (notes can be edited or deleted), and the scope is limited to personal metadata about other users.
Attacks that exploit this kind of access
Add a private note about a user. 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.
add_user_note accepts 2 parameters: text, username. 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 add_user_note: 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.
add_user_note 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 add_user_note 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 add_user_note. 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.
add_user_note 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 →