Gets detailed information about a specific member in a Discord server
AI agents call discord_get_member to retrieve information from MCP-Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves member data without side effects. It performs a read-only query operation that returns information about a Discord server member. There is no data modification, irreversible action, or external operation execution involved. The low severity reflects that member information is typically non-sensitive or already discoverable within a Discord server context.
From the tool's definition Tool description states it 'Gets detailed information about a specific member in a Discord server' — a pure retrieval operation with no modification, deletion, or execution of code/commands.
Documented attack patterns abuse exactly the kind of access discord_get_member gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Discord, and nothing reaches the server without passing your rules. This is the rule we recommend for discord_get_member:
{
"version": "1",
"default": "deny",
"tools": {
"discord_get_member": {}
}
} discord_get_member 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.
Gets detailed information about a specific member in a Discord server. It is categorised as a Read tool in the MCP-Discord MCP Server, which means it retrieves data without modifying state.
Register the MCP-Discord MCP server in PolicyLayer and add a rule for discord_get_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 MCP-Discord. Nothing to install.
discord_get_member 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 discord_get_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 discord_get_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.
discord_get_member is provided by the MCP-Discord MCP server (barryyip0625/mcp-discord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-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.
43 MCP-Discord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.