Stream incoming Lichess events such as game starts, incoming challenges, and correspondence game moves.
AI agents call lichess_stream_events 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 real-time event data from Lichess but does not modify state, execute operations, or create side effects. It is informational only, similar to subscribing to notifications. Even in adversarial use, an AI agent receiving this data stream cannot cause harm—at worst, it gains situational awareness of what is happening on the platform. Classified as Read with low severity.
From the tool's definition Tool streams incoming events (game starts, challenges, correspondence moves) without taking action. Description uses passive language: 'incoming', 'stream'. No mutation, deletion, execution, or financial operations described.
Attacks that exploit this kind of access
Stream incoming Lichess events such as game starts, incoming challenges, and correspondence game moves. 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_stream_events: 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_stream_events 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_stream_events 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_stream_events. 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_stream_events 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 →