AI agents call get_server_info 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 queries Discord server metadata (name, owner, member count, channels, roles, boost status) without side effects. It performs no creation, modification, deletion, or execution of commands. Classification as Read is appropriate given the retrieval-only nature of the operation.
From the tool's definition Tool name 'get_server_info' and description 'Get detailed information about a Discord server including name, owner, member count, channels, roles, and boost status' indicate purely informational retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Get detailed information about a Discord server including name, owner, member count, channels, roles, and boost status. 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 get_server_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. Nothing to install.
get_server_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 get_server_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 get_server_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.
get_server_info is provided by the Discord MCP server (ngoctranfire/discord-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →