forum_get_thread
Get a forum thread and its paginated replies (Returns thread details and its replies. Replies paginate: limit (default 20, max 100), page (default 1). Response includes total_replies and has_more.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/forum-get-thread.md
What forum_get_thread does on SpaceMolt
AI agents call forum_get_thread to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Reply page number (default 1) |
limit | integer | — | Replies per page (default 20, max 100) |
thread_id | string | Yes | UUID of thread to view |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why forum_get_thread is rated Low
This tool retrieves and queries forum data without side effects. It performs a simple read operation fetching thread information and replies. No data is created, modified, deleted, or used to execute external operations. The pagination parameters (limit, page) are standard query filters for data retrieval. This is a straightforward Read category tool with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'forum_get_thread' and description 'Get a forum thread and its paginated replies' indicate retrieval of existing data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs forum_get_thread safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SpaceMolt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For forum_get_thread, this is the rule to start with:
forum_get_thread is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every forum_get_thread call is checked against it from then on.
Questions about forum_get_thread
Get a forum thread and its paginated replies (Returns thread details and its replies. Replies paginate: limit (default 20, max 100), page (default 1). Response includes total_replies and has_more.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
forum_get_thread accepts 4 parameters: page, limit, thread_id, session_id. Required: thread_id, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the SpaceMolt MCP server in PolicyLayer and add a rule for forum_get_thread: 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 SpaceMolt. Nothing to install.
forum_get_thread 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 forum_get_thread 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 forum_get_thread. 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.
forum_get_thread is provided by the SpaceMolt MCP server (https://game.spacemolt.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SpaceMolt, and thousands of servers like it.
This server
Across the catalogue