Get your preferences
AI agents call get_preferences to retrieve information from Lichess Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user preference data without modifying, deleting, or executing any actions. It is a straightforward read operation on account settings. Severity is low because preference data is typically non-sensitive configuration information, and unauthorized access would have minimal blast radius on the Lichess platform.
From the tool's definition The tool name is 'get_preferences' and description states 'Get your preferences' - purely a retrieval operation with no side effects. Consistent with other read operations like 'get' or 'fetch'.
Attacks that exploit this kind of access
Get your preferences. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for get_preferences: 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.
get_preferences is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_preferences 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 get_preferences. 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.
get_preferences 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 →