Get members of a team
AI agents call get_team_members 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 |
|---|---|---|---|
max | number | — | Maximum number of members to fetch |
teamId | string | — | The team ID |
Parameters from the server's own tool schema.
This tool retrieves team membership information, which is a read-only operation. There are no side effects, data modifications, destructive actions, financial transactions, or code execution involved. The blast radius of misuse is minimal—an AI agent obtaining team member lists poses no significant risk to the Lichess platform or user accounts.
From the tool's definition Tool name is 'get_team_members' and description states 'Get members of a team' — this is a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get members of a team. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_team_members accepts 2 parameters: max, 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_members: 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_members 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_members 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_members. 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_members 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 →