Allow to read discussion from a channel. Return the messages exactly as received without summarizing
AI agents call read_message to retrieve information from Discord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves message history from Discord channels without creating, modifying, or deleting any data. It is a straightforward read operation that queries existing data and returns it verbatim. The low severity reflects minimal risk—the primary concern would be accessing sensitive information already in Discord, which is a baseline information disclosure risk rather than operational harm.
From the tool's definition Tool name 'read_message' and description 'Allow to read discussion from a channel. Return the messages exactly as received' explicitly indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Allow to read discussion from a channel. Return the messages exactly as received without summarizing. It is categorised as a Read tool in the Discord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP Server MCP server in PolicyLayer and add a rule for read_message: 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 MCP Server. Nothing to install.
read_message 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 read_message 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 read_message. 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.
read_message is provided by the Discord MCP Server MCP server (userdeter1/mcp-discord). 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 →