Get join requests for a team
AI agents call get_team_join_requests 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 join requests to a team without creating, modifying, deleting, or executing any operations. It is a query operation that returns data for viewing purposes only, making it a Read category tool with low severity since exposing team join request information poses minimal risk even if misused by an unauthorized agent.
From the tool's definition Tool name 'get_team_join_requests' and description 'Get join requests for a team' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get join requests for 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_join_requests 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_join_requests: 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_join_requests 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_join_requests 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_join_requests. 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_join_requests 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 →