Opening explorer. scope: "lichess" (community), "masters" (top 2200+ humans), "player" (single user). As of mid-2026 Lichess began requiring a Personal API Token on every explorer.lichess.ovh request — pass yours via _apiKey. Create one (free) at https://lichess.org/account/oauth/token; no scopes...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Lichess server.
Free to start. No card required.
AI agents use opening_explorer to create or modify resources in Lichess. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call opening_explorer repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Lichess.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"opening_explorer": {
"limits": [
{
"counter": "opening_explorer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Lichess policy for all 30 tools.
These attack patterns abuse exactly the kind of access opening_explorer gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Opening explorer. scope: "lichess" (community), "masters" (top 2200+ humans), "player" (single user). As of mid-2026 Lichess began requiring a Personal API Token on every explorer.lichess.ovh request — pass yours via _apiKey. Create one (free) at https://lichess.org/account/oauth/token; no scopes required for read-only Explorer access.. It is categorised as a Write tool in the Lichess MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lichess MCP server in PolicyLayer and add a rule for opening_explorer: 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. Nothing to install.
opening_explorer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the opening_explorer 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 opening_explorer. 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.
opening_explorer is provided by the Lichess MCP server (https://gateway.pipeworx.io/lichess/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Lichess tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.