Fetch recent games for a Lichess user in a simple text-friendly format.
AI agents call fetch-lichess-games to retrieve information from ChessAgine MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical game data from Lichess for a specified user. It is a read-only operation that queries and returns data without creating, modifying, deleting, or executing any operations. The worst-case misuse would be unauthorized access to user game history, which has minimal security impact since Lichess game records are typically public or semi-public. Classified as Read with low severity.
From the tool's definition Tool name 'fetch-lichess-games' and description 'Fetch recent games for a Lichess user in a simple text-friendly format' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Fetch recent games for a Lichess user in a simple text-friendly format. It is categorised as a Read tool in the ChessAgine MCP MCP Server, which means it retrieves data without modifying state.
Register the ChessAgine MCP server in PolicyLayer and add a rule for fetch-lichess-games: 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 ChessAgine MCP. Nothing to install.
fetch-lichess-games 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 fetch-lichess-games 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 fetch-lichess-games. 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.
fetch-lichess-games is provided by the ChessAgine MCP server (jalpp/chessagine-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 →