Discover Discourse forum communities by topic or find similar communities.
AI agents call search_discourse_communities 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 or queries data about Discourse communities (search, discover, find) with no side effects. It performs a read-only operation that does not create, modify, delete, or execute any code. The action is passive discovery of existing community metadata.
From the tool's definition Tool name 'search_discourse_communities' and description 'Discover Discourse forum communities by topic or find similar communities' indicate retrieval of forum community information without modification.
Attacks that exploit this kind of access
Discover Discourse forum communities by topic or find similar communities. 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 search_discourse_communities: 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.
search_discourse_communities 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 search_discourse_communities 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 search_discourse_communities. 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.
search_discourse_communities 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 →