Disconnect a member from their current voice channel.
AI agents invoke disconnect_from_voice to trigger actions in Discord. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool forcibly removes a user from a voice channel, which is an active operation with immediate real-world effects on a Discord member's session. It's not purely destructive (data isn't deleted), but it executes an administrative action against a user. The blast radius is high because it could be misused to disrupt legitimate users or harass members at scale in a server with many members.
From the tool's definition Disconnect a member from their current voice channel
Documented attack patterns abuse exactly the kind of access disconnect_from_voice gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord, and nothing reaches the server without passing your rules. This is the rule we recommend for disconnect_from_voice:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect_from_voice": {
"limits": [
{
"counter": "disconnect_from_voice_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} disconnect_from_voice stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnect a member from their current voice channel. It is categorised as a Execute tool in the Discord MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Discord MCP server in PolicyLayer and add a rule for disconnect_from_voice: 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.
disconnect_from_voice is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the disconnect_from_voice 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 disconnect_from_voice. 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.
disconnect_from_voice is provided by the Discord MCP server (hardheadhackerhead/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
139 Discord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.