List incoming and outgoing challenges
AI agents call list_challenges 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 and displays existing challenge data without modifying, deleting, or executing any operations. It is purely informational and has no blast radius if misused by an AI agent—the worst outcome would be reading challenge information the user already has access to.
From the tool's definition Tool name 'list_challenges' and description 'List incoming and outgoing challenges' indicate a retrieval operation with no side effects. The verb 'list' and the action of retrieving challenge data confirms this is a query-only function.
Attacks that exploit this kind of access
List incoming and outgoing challenges. 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 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 Integration. Nothing to install.
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 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 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.
list_challenges 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 →