AI agents use discord_set_role_permission 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 Discord's permission system by creating or updating permission overwrites for roles on specific channels. While it can have significant impact on server security and access control, it is reversible (permissions can be changed again). The operation does not delete, destroy, execute arbitrary code, or move financial assets.
From the tool's definition The tool "Add or update a per-channel permission overwrite for a role, allowing and/or denying specific permissions" modifies access control rules and permissions.
Attacks that exploit this kind of access
Add or update a per-channel permission overwrite for a role, allowing and/or denying specific permissions. Merges with the role. 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_role_permission: 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_role_permission 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_role_permission 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_role_permission. 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_role_permission 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 →