List your incoming and outgoing chess challenges on Lichess. See pending game invites you have received or sent.
AI agents call lichess_list_challenges 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 queries and displays challenge data without modifying, deleting, or executing any actions. It is a simple informational read operation analogous to fetching a list of pending items. The blast radius of misuse is minimal—an attacker could only view challenge metadata, which has no financial, destructive, or operational consequences.
From the tool's definition Tool description states 'List your incoming and outgoing chess challenges' and 'See pending game invites' — purely retrieval operations with no side effects.
Attacks that exploit this kind of access
List your incoming and outgoing chess challenges on Lichess. See pending game invites you have received or sent. 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_list_challenges: 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_list_challenges 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_list_challenges 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_list_challenges. 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_list_challenges 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 →