AI agents use modify_member 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 creates or modifies data reversibly within a Discord server—it changes member attributes without permanently destroying data. While high-severity due to the potential blast radius (incorrect role assignments or member timeouts could significantly disrupt server operations), it is not Destructive (reversible), Financial, or Execute (no arbitrary code execution).
From the tool's definition modify_member can modify member properties including nickname, roles, and timeout settings. The description explicitly states these are modifications to member properties, which are reversible (roles can be reassigned, nicknames changed back, timeouts…
Attacks that exploit this kind of access
Modify member properties (nickname, roles, timeout, etc.). 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 modify_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.
modify_member 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 modify_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 modify_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.
modify_member is provided by the Discord MCP server (scarecr0w12/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 →