Get official broadcasts (TV shows)
AI agents call get_official_broadcasts 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 public broadcast information from the Lichess platform. It does not create, modify, delete, or execute any operations—it simply queries and returns data about official broadcasts. There are no side effects or irreversible actions possible, making this a straightforward Read operation with low risk.
From the tool's definition Tool name 'get_official_broadcasts' and description 'Get official broadcasts (TV shows)' indicate a retrieval operation with no side effects. The verb 'Get' and the context of fetching broadcast data confirm this is a read-only query.
Attacks that exploit this kind of access
Get official broadcasts (TV shows). 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_official_broadcasts: 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_official_broadcasts 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_official_broadcasts 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_official_broadcasts. 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_official_broadcasts 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 →