decline_join_request · Lichess Integration MCP

WHAT IT DOES

What decline_join_request does on Lichess Integration

AI agents use decline_join_request 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
`userId`	string	—	The user ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why decline_join_request needs a policy

Declining a join request modifies the state of the join request (rejecting it) and affects the user's ability to join the team. While this action has consequences for the requesting user, it is a reversible moderation action (the user could submit a new request), placing it in the Write category rather than Destructive.

From the tool's definition Decline a join request for your team

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

decline_join_request Rate-limited

decline_join_request 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": {
    "decline_join_request": {
      "limits": [
        {
          "counter": "decline_join_request_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 decline_join_request

What does the decline_join_request tool do? +

Decline a join request for your 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 decline_join_request accept? +

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

How do I enforce a policy on decline_join_request? +

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

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

Can I rate-limit decline_join_request? +

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

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

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