Get a paginated list of posts and replies by a specific user, with the most recent first. Returns 30 posts per page. Includes topic title, post date, excerpt, and direct links.
AI agents call discourse_list_user_posts 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 queries and returns existing forum data without side effects. It is a straightforward read operation that retrieves public or user-accessible post history. The low severity reflects minimal blast radius—an agent misusing this could retrieve unwanted user data, but cannot modify, delete, or execute actions.
From the tool's definition Tool retrieves a 'paginated list of posts and replies by a specific user' with 'topic title, post date, excerpt, and direct links.' The description uses only retrieval verbs: 'get', 'returns'. No modification, deletion, or execution is described.
Attacks that exploit this kind of access
Get a paginated list of posts and replies by a specific user, with the most recent first. Returns 30 posts per page. Includes topic title, post date, excerpt, and direct links. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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 →