This record as markdown: /tools/io-github-portel-dev-ncp/manage-roles.md
What manage_roles does on Ncp
AI agents use manage_roles to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why manage_roles is rated Medium
Managing roles is a write operation that modifies user permissions and access levels in a Discord server. While not destructive (roles can be reassigned), and not financial, this has significant blast radius if misused by an AI agent—it could grant excessive privileges, remove user access, or disrupt server administration.
From the tool's definition Tool name 'manage_roles' and description 'Manage user roles in Discord server' indicate the ability to create, modify, or assign user roles. This is a write operation that alters access control and permissions.
Attacks that exploit this kind of access
The rule that runs manage_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_roles, this is the rule to start with:
manage_roles 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every manage_roles call is checked against it from then on.
Questions about manage_roles
Manage user roles in Discord server. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for manage_roles: 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 Ncp. Nothing to install.
manage_roles 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 manage_roles 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 manage_roles. 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.
manage_roles is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue