Check if you are authenticated with Lichess and return account info. Use this to verify login status or confirm which Lichess chess account is connected.
AI agents call lichess_auth_status to retrieve information from Lichess MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication and account information without modifying any data, executing commands, or performing any irreversible actions. It is a simple status check that returns existing data about the current session, making it a Read category tool with low severity.
From the tool's definition Tool name is 'lichess_auth_status' and description states it 'Check[s] if you are authenticated' and 'return[s] account info' and 'verify login status or confirm which Lichess chess account is connected.' These are all read-only query operations with no side…
Attacks that exploit this kind of access
Check if you are authenticated with Lichess and return account info. Use this to verify login status or confirm which Lichess chess account is connected. It is categorised as a Read tool in the Lichess MCP MCP Server, which means it retrieves data without modifying state.
Register the Lichess MCP server in PolicyLayer and add a rule for lichess_auth_status: 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 MCP. Nothing to install.
lichess_auth_status 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 lichess_auth_status 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 lichess_auth_status. 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.
lichess_auth_status is provided by the Lichess MCP server (jamespdaily/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 →