Push PGN to a broadcast round
AI agents use push_broadcast_round_pgn to create or update resources in Lichess Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess Integration environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
pgn | string | — | PGN games to push |
roundId | string | — | ID of the round |
broadcastId | string | — | ID of the broadcast |
Parameters from the server's own tool schema.
This tool creates or modifies data on the Lichess platform by pushing/uploading PGN game data to a broadcast round. It is reversible (the PGN can be corrected or removed), so it falls under Write rather than Destructive. The blast radius is moderate—an AI agent could push incorrect or spam game data to a broadcast, but this would not cause financial loss or execute arbitrary code.
From the tool's definition Tool name contains 'push' and description states 'Push PGN to a broadcast round', indicating it uploads/writes data to a broadcast round. PGN (Portable Game Notation) is a standard format for recording chess games.
Attacks that exploit this kind of access
Push PGN to a broadcast round. It is categorised as a Write tool in the Lichess Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
push_broadcast_round_pgn accepts 3 parameters: pgn, 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 push_broadcast_round_pgn: 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.
push_broadcast_round_pgn 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 push_broadcast_round_pgn 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 push_broadcast_round_pgn. 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.
push_broadcast_round_pgn 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 →