Assign a role to a member in a Discord guild. Defaults to dry-run mode.
AI agents use discord.role.assign to create or update resources in Discord MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discord MCP Server environment.
This tool modifies a guild member's roles by assigning a new role, which is a reversible write operation (roles can be removed). The dry-run default slightly reduces immediate risk, but misuse could grant elevated permissions to members. Severity is medium because improper role assignment could lead to privilege escalation within a Discord server.
From the tool's definition 'Assign a role to a member in a Discord guild. Defaults to dry-run mode.'
Documented attack patterns abuse exactly the kind of access discord.role.assign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for discord.role.assign:
{
"version": "1",
"default": "deny",
"tools": {
"discord.role.assign": {
"limits": [
{
"counter": "discord.role.assign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}discord.role.assign 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.
Assign a role to a member in a Discord guild. Defaults to dry-run mode. It is categorised as a Write tool in the Discord MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Discord MCP Server MCP server in PolicyLayer and add a rule for discord.role.assign: 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 MCP Server. Nothing to install.
discord.role.assign 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 discord.role.assign 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.role.assign. 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.role.assign is provided by the Discord MCP Server MCP server (rastrian/discordmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord MCP Server, 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.
45 Discord MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.