Get information about a user in a server: username, display name, when they joined, and their roles.
AI agents call discord_user_info to retrieve information from Discord User without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns user profile data from Discord. It does not create, modify, delete, or execute any actions. The information retrieved is typically public or semi-public within a server context, and there are no irreversible consequences from invoking it. The low severity reflects that user information disclosure has limited blast radius compared to tools that modify messages or delete content.
From the tool's definition Tool retrieves user metadata (username, display name, join date, roles) with no modification or side effects. Description explicitly uses 'Get information' indicating a read-only query operation.
Documented attack patterns abuse exactly the kind of access discord_user_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord User, and nothing reaches the server without passing your rules. This is the rule we recommend for discord_user_info:
{
"version": "1",
"default": "deny",
"tools": {
"discord_user_info": {}
}
} discord_user_info 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.
Get information about a user in a server: username, display name, when they joined, and their roles. It is categorised as a Read tool in the Discord User MCP Server, which means it retrieves data without modifying state.
Register the Discord User MCP server in PolicyLayer and add a rule for discord_user_info: 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 User. Nothing to install.
discord_user_info 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_user_info 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_user_info. 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_user_info is provided by the Discord User MCP server (olivier-motium/discord-user-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord User, 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.
16 Discord User tools catalogued and risk-classified — across an index of 43,000+ MCP servers.