Show all permissions a member has server-wide, including their roles.
AI agents call list_member_permissions to retrieve information from Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays permission information about a Discord member. It is purely informational—it reads existing data without creating, modifying, deleting, or executing any actions. This is a typical Read category tool with low severity because disclosing permissions information has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_member_permissions' and description 'Show all permissions a member has server-wide, including their roles' indicate a query/retrieval operation with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access list_member_permissions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord, and nothing reaches the server without passing your rules. This is the rule we recommend for list_member_permissions:
{
"version": "1",
"default": "deny",
"tools": {
"list_member_permissions": {}
}
}list_member_permissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show all permissions a member has server-wide, including their roles. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP server in PolicyLayer and add a rule for list_member_permissions: 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.
list_member_permissions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_member_permissions 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 list_member_permissions. 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.
list_member_permissions is provided by the Discord MCP server (hardheadhackerhead/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
139 Discord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.