List all chat channels for the currently authenticated user, including both public channels they
AI agents call discourse_list_user_chat_channels 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 performs a data retrieval operation for the authenticated user's chat channels. It has no destructive, financial, or execution implications. The action is read-only, returning existing information without creating, modifying, or deleting any data. The blast radius of misuse is minimal—an agent can only view channels already accessible to that user.
From the tool's definition Tool name contains 'list', description states 'List all chat channels', and operation retrieves data without modification or side effects.
Attacks that exploit this kind of access
List all chat channels for the currently authenticated user, including both public channels they. 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_list_user_chat_channels: 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_list_user_chat_channels 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_list_user_chat_channels 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_list_user_chat_channels. 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_list_user_chat_channels 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 →