Get team information by ID
AI agents call get_team_info 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 |
|---|---|---|---|
teamId | string | — | The team ID |
Parameters from the server's own tool schema.
This tool retrieves information about a team on the Lichess platform. It queries existing data and returns it without modifying, executing code, deleting, or creating any obligations. The blast radius of misuse is minimal—an attacker could only view team information that may or may not be public, posing no direct harm to accounts or systems.
From the tool's definition Tool name 'get_team_info' and description 'Get team information by ID' indicate data retrieval with no side effects. The verb 'get' and the absence of any modification, deletion, or execution language confirm this is a read operation.
Attacks that exploit this kind of access
Get team information by ID. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_team_info accepts 1 parameter: teamId. 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_team_info: 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_team_info 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_team_info 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_team_info. 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_team_info 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 →