Move a member from their current voice channel to a different voice channel. The member must already be in a voice channel.
AI agents use move_to_voice to create or update resources in Discord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discord environment.
This tool modifies a member's state by relocating them between voice channels. It is reversible (the member can be moved back or can rejoin), so it falls under Write rather than Destructive. Misuse could disrupt users by forcibly moving them, giving it a medium severity.
From the tool's definition Move a member from their current voice channel to a different voice channel
Documented attack patterns abuse exactly the kind of access move_to_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 move_to_voice:
{
"version": "1",
"default": "deny",
"tools": {
"move_to_voice": {
"limits": [
{
"counter": "move_to_voice_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} move_to_voice 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.
Free to start. No card required.
Move a member from their current voice channel to a different voice channel. The member must already be in a voice channel. It is categorised as a Write tool in the Discord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Discord MCP server in PolicyLayer and add a rule for move_to_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.
move_to_voice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_to_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 move_to_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.
move_to_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.