AI agents use discord_set_nickname 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 member metadata (nickname) within a Discord guild. While the change is reversible and affects only a user's display name rather than data deletion or financial impact, it represents a write operation that alters guild state. Severity is medium because widespread misuse could disrupt guild usability and member identification, but the change is easily undone.
From the tool's definition Tool name 'discord_set_nickname' and description 'Set or clear a member' indicate modification of a member's nickname attribute. The verbs 'set' and 'clear' are reversible write operations.
Attacks that exploit this kind of access
Set or clear a member. 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 discord_set_nickname: 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_set_nickname 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_set_nickname 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_set_nickname. 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_set_nickname is provided by the Discord MCP server (@pasympa/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →