Search for teams
AI agents call search_teams 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 |
|---|---|---|---|
page | number | — | Page number (starting at 1) |
text | string | — | Search text |
Parameters from the server's own tool schema.
This tool performs a search/query operation on the Lichess platform to find teams. Search operations are retrieval-based with no side effects—they do not create, modify, delete, or execute any external operations. The blast radius of misuse is minimal, as an AI agent could only access publicly available team information.
From the tool's definition Tool name 'search_teams' and description 'Search for teams' indicates a read-only query operation that retrieves team information without modifying data.
Attacks that exploit this kind of access
Search for teams. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
search_teams accepts 2 parameters: page, text. 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 search_teams: 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.
search_teams 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 search_teams 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 search_teams. 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.
search_teams 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 →