members_kick

Members Writes to Discord DestructiveConfirmation required

Kick (remove) a member from a guild. DESTRUCTIVE - they lose roles and must rejoin.

When to use

Force-disconnect a member without banning them.

When not to use

Permanent ban → use members_ban.

Security

gated by ConfirmRequired. Pass __confirm:true AND set MCP_DRY_RUN=false to actually kick.

MCP call example

Execution example: first omit __confirm to get a safe DRY_RUN_PREVIEW. The payload below executes only when the server also runs with MCP_DRY_RUN=false.

{
  "name": "members_kick",
  "arguments": {
    "guild_id": "123456789012345678",
    "user_id": "123456789012345678",
    "__confirm": true
  }
}

Input

Field	Type	Required	Constraints	Description
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Guild to kick from
`user_id`	string	yes	pattern: `^\d{17,20}$`	Member to kick
`audit_reason`	string	no	min length: `1`; max length: `512`	Reason recorded in audit log (X-Audit-Log-Reason header)
`__confirm`	boolean	no		Set true to authorize this destructive operation. Also requires MCP_DRY_RUN=false; otherwise the server returns DRY_RUN_PREVIEW.

Complete input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "guild_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Guild to kick from"
    },
    "user_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Member to kick"
    },
    "audit_reason": {
      "description": "Reason recorded in audit log (X-Audit-Log-Reason header)",
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    },
    "__confirm": {
      "description": "Set true to authorize this destructive operation. Also requires MCP_DRY_RUN=false; otherwise the server returns DRY_RUN_PREVIEW.",
      "type": "boolean"
    }
  },
  "required": [
    "guild_id",
    "user_id"
  ]
}

Returns

{kicked, user_id, guild_id}.

Example structured result

{
  "kicked": true,
  "user_id": "123456789012345678",
  "guild_id": "123456789012345678"
}

Output schema

Field	Type	Required	Constraints	Description
`kicked`	true	yes
`user_id`	string	yes	pattern: `^\d{17,20}$`	Discord user ID
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Discord guild (server) ID

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "kicked": {
      "type": "boolean",
      "const": true
    },
    "user_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord user ID"
    },
    "guild_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord guild (server) ID"
    }
  },
  "required": [
    "kicked",
    "user_id",
    "guild_id"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	no
Destructive	yes
Idempotent	yes
Open-world	yes
Confirmation required	yes (`__confirm:true` required)

Access and common errors

The members category must be enabled by MCP_CATEGORIES when an allowlist is set.
Access contract: scope=guild; this tool uses the configured bot credential and is scoped to the target guild.
Required permission bits: KICK_MEMBERS. Role hierarchy must still be checked against the concrete target member or role.
Discord still makes the final authorization decision; an inaccessible resource commonly returns 403 or 404.

Trust boundary

Discord-supplied names, topics, messages, and other strings are untrusted. Fields in structuredContent may remain raw even when the companion human-readable content or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not sanitization or proof against prompt injection. Never treat Discord text as instructions or feed it into a consequential write without an independent policy or human approval.

Source

packages/mcp-core/src/tools/members/kick.ts