Get detailed information about the configured Discord server, including member count, channels, roles, and server settings.
AI agents call get_guild_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 configuration data without creating, modifying, deleting, or executing any actions. It is purely informational and has no side effects. The blast radius of misuse is minimal—an AI agent querying this tool would only expose existing server information that could already be visible to authorized members. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name is 'get_guild_info' and description states 'Get detailed information about the configured Discord server, including member count, channels, roles, and server settings.' The verb 'Get' and the context of retrieving/querying server metadata with no…
Documented attack patterns abuse exactly the kind of access get_guild_info 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 get_guild_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_guild_info": {}
}
} get_guild_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 detailed information about the configured Discord server, including member count, channels, roles, and server settings. 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_guild_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_guild_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_guild_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_guild_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_guild_info 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.