Search Discourse site content including topics, posts, and users. Use search operators like @username, #tag, category:name for filtered results.
AI agents call discourse_search 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 is a straightforward search/query operation that retrieves data from the Discourse forum without side effects. It enables information discovery but does not create, modify, delete, or execute any changes. The severity is low because search operations have minimal blast radius—worst case exposes already-public forum data that users can access directly.
From the tool's definition Tool performs 'Search Discourse site content including topics, posts, and users' with search operators for filtering. No modification, deletion, execution, or financial operations are mentioned or implied.
Attacks that exploit this kind of access
Search Discourse site content including topics, posts, and users. Use search operators like @username, #tag, category:name for filtered results. 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_search: 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_search 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_search 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_search. 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_search 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 →