leave_team · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What leave_team does on Lichess Integration

AI agents use leave_team to create or update resources in Lichess Integration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lichess Integration environment.

PARAMETERS

Parameter	Type	Required	Description
`teamId`	string	—	The team ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why leave_team needs a policy

Leaving a team is a reversible action (the user can rejoin, assuming the team allows it), making it a Write operation. The blast radius is medium because it could cause the user to lose team benefits, standings, or access to team tournaments, but it is not irreversible data destruction.

From the tool's definition 'Leave a team' - this modifies membership state by removing the user from a team

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

leave_team Rate-limited

leave_team stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "leave_team": {
      "limits": [
        {
          "counter": "leave_team_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lichess Integration, so you can run agents against it safely.

FAQ

Questions about leave_team

What does the leave_team tool do? +

Leave a team. It is categorised as a Write tool in the Lichess Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does leave_team accept? +

leave_team accepts 1 parameter: teamId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on leave_team? +

Register the Lichess Integration MCP server in PolicyLayer and add a rule for leave_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.

What risk level is leave_team? +

leave_team is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit leave_team? +

Yes. Add a rate_limit block to the leave_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.

How do I block leave_team completely? +

Set action: deny in the PolicyLayer policy for leave_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.

What MCP server provides leave_team? +

leave_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.