Validate and select a Discourse site for subsequent tool calls. Verifies the site is reachable and retrieves its title. Must be called before using other tools when multiple sites are configured.
AI agents call discourse_select_site 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 reads/validates connectivity to a Discourse site and retrieves its title. It sets a session-level context but does not create, modify, or delete any data. The action is purely informational/configurational with no side effects on the forum data.
From the tool's definition Validate and select a Discourse site... Verifies the site is reachable and retrieves its title
Attacks that exploit this kind of access
Validate and select a Discourse site for subsequent tool calls. Verifies the site is reachable and retrieves its title. Must be called before using other tools when multiple sites are configured. 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_select_site: 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_select_site 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_select_site 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_select_site. 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_select_site 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 →