join_swiss · Lichess Integration MCP: Risk & Policy

WHAT IT DOES

What join_swiss does on Lichess Integration

AI agents use join_swiss 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
`swissId`	string	—	Swiss tournament ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why join_swiss needs a policy

Joining a tournament is a reversible write action that creates a participation record on the platform. It does not delete data, execute code, or involve financial transactions. Misuse could lead to unwanted tournament registrations but is generally low-impact and reversible.

From the tool's definition Join a Swiss tournament — registers/enrolls the user in a tournament, creating a new participation record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

join_swiss Rate-limited

join_swiss 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_swiss": {
      "limits": [
        {
          "counter": "join_swiss_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_swiss

What does the join_swiss tool do? +

Join a Swiss tournament. 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_swiss accept? +

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

How do I enforce a policy on join_swiss? +

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

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

Can I rate-limit join_swiss? +

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

Set action: deny in the PolicyLayer policy for join_swiss. 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_swiss? +

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