Get messages from a chat channel with flexible pagination and date-based filtering. Supports: (1) paginating with direction=
AI agents call discourse_get_chat_messages to retrieve information from Discourse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing chat messages with flexible pagination and date-based filtering. No side effects are present—it does not create, modify, delete, or execute operations. It is a straightforward data retrieval operation, making it a Read-category tool with low severity since message retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'Get messages from a chat channel' with pagination and filtering capabilities. The verb 'Get' and the read-only nature of retrieving chat messages with no modification or deletion described.
Attacks that exploit this kind of access
Get messages from a chat channel with flexible pagination and date-based filtering. Supports: (1) paginating with direction=. It is categorised as a Read tool in the Discourse MCP MCP Server, which means it retrieves data without modifying state.
Register the Discourse MCP server in PolicyLayer and add a rule for discourse_get_chat_messages: 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 Discourse MCP. Nothing to install.
discourse_get_chat_messages 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 discourse_get_chat_messages 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 discourse_get_chat_messages. 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.
discourse_get_chat_messages is provided by the Discourse MCP server (king-of-the-grackles/discourse-mcp). 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 →