Get all TV channels and their current games
AI agents call get_tv_channels 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 publicly available information about TV channels and ongoing games on the Lichess platform. It performs no modifications, deletions, executions, or financial operations. The blast radius of misuse is minimal—an AI agent can only retrieve data it is already authorized to view, with no ability to alter state or cause harm.
From the tool's definition Tool name 'get_tv_channels' and description 'Get all TV channels and their current games' indicate a retrieval operation with no side effects. The verb 'Get' and the passive observation of 'current games' confirm this is a read-only query.
Attacks that exploit this kind of access
Get all TV channels and their current games. 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_tv_channels: 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_tv_channels 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_tv_channels 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_tv_channels. 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_tv_channels 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 →