join_team · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What join_team does on Lichess Integration

AI agents use join_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
`message`	string	—	Optional message for team leaders

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why join_team needs a policy

Joining a team is a reversible write action (membership can be undone by leaving the team). It creates a new association/record but does not delete data or execute code. Severity is low as the blast radius of misuse is minimal.

From the tool's definition Join a team — creates a membership/association between the user and a team on Lichess

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

join_team Rate-limited

join_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": {
    "join_team": {
      "limits": [
        {
          "counter": "join_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 join_team

What does the join_team tool do? +

Join 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 join_team accept? +

join_team accepts 2 parameters: teamId, message. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on join_team? +

Register the Lichess Integration MCP server in PolicyLayer and add a rule for join_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 join_team? +

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

Can I rate-limit join_team? +

Yes. Add a rate_limit block to the join_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 join_team completely? +

Set action: deny in the PolicyLayer policy for join_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 join_team? +

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