Get one round of a broadcast
AI agents call get_broadcast_round 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
roundId | string | — | ID of the round |
broadcastId | string | — | ID of the broadcast |
Parameters from the server's own tool schema.
This tool retrieves information about a broadcast round from the Lichess platform. It performs no modifications, deletions, or state changes. The blast radius of misuse is minimal—an agent could only retrieve broadcast data that is already public on Lichess. This is a straightforward Read operation.
From the tool's definition Tool name 'get_broadcast_round' and description 'Get one round of a broadcast' indicate a retrieval operation with no side effects. The verb 'get' and the read-only nature of fetching broadcast information confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get one round of a broadcast. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_broadcast_round accepts 2 parameters: roundId, broadcastId. The full parameter table on this page comes from the server's own tool schema.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for get_broadcast_round: 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_broadcast_round 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_broadcast_round 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_broadcast_round. 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_broadcast_round 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 →