Get recently started simuls
AI agents call get_current_simuls 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 information about currently active simultaneous exhibitions on Lichess without modifying, executing, or deleting anything. It is a straightforward read operation with minimal security risk—the worst case is unauthorized access to public or semi-public tournament information, which has negligible blast radius.
From the tool's definition Tool name 'get_current_simuls' and description 'Get recently started simuls' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying simul (simultaneous exhibition) status confirms this is a data query.
Attacks that exploit this kind of access
Get recently started simuls. 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 get_current_simuls: 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.
get_current_simuls 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 get_current_simuls 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 get_current_simuls. 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.
get_current_simuls 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 →