discord_kick_member
Kick a member from a guild (requires confirm=true)
This record as markdown: /tools/arrrnmp-discord-mcp/discord-kick-member.md
What discord_kick_member does on Discord
AI agents call discord_kick_member to permanently remove resources in Discord, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why discord_kick_member is rated Critical
Kicking a member expels them from the Discord server. While the member could theoretically rejoin (unlike a ban), the action itself is an irreversible expulsion from the guild that cannot be undone by the tool — making it Destructive. The high severity reflects the social/community impact of wrongly kicking members at scale.
From the tool's definition 'Kick a member from a guild' — removes a user from the server, an action that is irreversible without the member rejoining themselves; 'requires confirm=true' indicates awareness of the destructive nature.
Attacks that exploit this kind of access
The rule that runs discord_kick_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Discord, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For discord_kick_member, this is the rule to start with:
discord_kick_member is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Discord, apply this rule, and every discord_kick_member call is checked against it from then on.
Questions about discord_kick_member
Kick a member from a guild (requires confirm=true). It is categorised as a Destructive tool in the Discord MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Discord MCP server in PolicyLayer and add a rule for discord_kick_member: 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 Discord. Nothing to install.
discord_kick_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the discord_kick_member 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.
Set action: deny in the PolicyLayer policy for discord_kick_member. 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.
discord_kick_member is provided by the Discord MCP server (arrrnmp/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Discord, and thousands of servers like it.
Across the catalogue