Get current tournaments
AI agents call get_arena_tournaments 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 queries tournament information from the Lichess platform without modifying, creating, executing commands, or deleting any data. It is a simple read operation that retrieves publicly available or user-accessible tournament listings. The blast radius of misuse is minimal—at worst, an AI agent could retrieve tournament data, which poses no security or operational risk.
From the tool's definition Tool name 'get_arena_tournaments' and description 'Get current tournaments' indicate a retrieval operation with no side effects. The verb 'Get' and context of querying tournament information align with data retrieval.
Attacks that exploit this kind of access
Get current tournaments. 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_arena_tournaments: 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_arena_tournaments 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_arena_tournaments 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_arena_tournaments. 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_arena_tournaments 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 →