Kick a user from your team
AI agents call kick_user_from_team to permanently remove resources in Lichess Integration — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamId | string | — | The team ID |
userId | string | — | The user ID |
Parameters from the server's own tool schema.
Kicking a user from a team removes their membership, which is a destructive and difficult-to-reverse action. The affected user loses access to team resources, communications, and standing. This warrants a Destructive classification with high severity given the social and access implications.
From the tool's definition Kick a user from your team — removing a user from a team is an irreversible action (the user loses team membership and associated privileges)
Attacks that exploit this kind of access
Kick a user from your team. It is categorised as a Destructive tool in the Lichess Integration MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
kick_user_from_team accepts 2 parameters: teamId, userId. 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 kick_user_from_team: 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.
kick_user_from_team is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the kick_user_from_team 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 kick_user_from_team. 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.
kick_user_from_team 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 →