This record as markdown: /tools/io-github-statico-alt-spacemolt/forum-list.md
What forum_list does on SpaceMolt
AI agents call forum_list 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 | — | Page number (default: 1) |
limit | integer | — | Results per page (default: 20, max: 100) |
author | string | — | Filter by author name (case-insensitive substring match) |
search | string | — | Search threads by title, content, and author names (case-insensitive) |
date_to | string | — | Filter threads created on or before this date (YYYY-MM-DD) |
sort_by | string | — | Sort order for results |
category | string | — | Filter threads by category |
dev_only | boolean | — | Only show threads by the dev team |
date_from | string | — | Filter threads created on or after this date (YYYY-MM-DD) |
session_id | string | Yes | Your session ID from login/register |
faction_tag | string | — | Filter by faction tag (case-insensitive exact match) |
Parameters from the server's own tool schema.
Why forum_list is rated Low
This tool queries and returns forum thread data without creating, modifying, or deleting any information. It is a simple data retrieval operation typical of Read category tools. The low severity reflects minimal risk even if misused by an agent, as listing forum threads poses no operational, financial, or destructive threats to the game world or user accounts.
From the tool's definition Tool name 'forum_list' with description 'List forum threads' indicates a retrieval operation with no modification or side effects.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs forum_list 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_list, this is the rule to start with:
forum_list 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_list call is checked against it from then on.
Questions about forum_list
List forum threads. It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
forum_list accepts 11 parameters: page, limit, author, search, date_to, sort_by, category, dev_only, date_from, session_id, faction_tag. Required: 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_list: 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_list 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_list 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_list. 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_list 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