Low Risk

discord_list_roles

List all roles in a guild

How to control discord_list_roles ↓

AI agents call discord_list_roles to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a read-only operation on Discord guild data. It retrieves and displays existing roles without creating, modifying, deleting, or executing any actions. The blast radius is minimal—an AI agent listing roles cannot cause harm beyond exposing role structure information that is typically visible to authorized guild members anyway.

From the tool's definition Tool name 'discord_list_roles' and description 'List all roles in a guild' indicate a query operation that retrieves role information without modification.

Documented attack patterns abuse exactly the kind of access discord_list_roles gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for discord_list_roles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "discord_list_roles": {}
  }
}

discord_list_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the discord_list_roles tool do? +

List all roles in a guild. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on discord_list_roles? +

Register the Sage MCP server in PolicyLayer and add a rule for discord_list_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 Sage MCP. Nothing to install.

What risk level is discord_list_roles? +

discord_list_roles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit discord_list_roles? +

Yes. Add a rate_limit block to the discord_list_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.

How do I block discord_list_roles completely? +

Set action: deny in the PolicyLayer policy for discord_list_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.

What MCP server provides discord_list_roles? +

discord_list_roles is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.