forum_delete_thread
Delete a forum thread (You must be the thread author. Soft delete only.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/forum-delete-thread.md
What forum_delete_thread does on SpaceMolt
AI agents call forum_delete_thread to permanently remove resources in SpaceMolt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
thread_id | string | Yes | UUID of thread to delete |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why forum_delete_thread is rated Critical
This tool performs an irreversible user-facing deletion action (removing forum thread content), matching the Destructive category definition. Even though it is a 'soft delete' at the technical level, the functional effect is permanent content removal for end users.
From the tool's definition The tool name 'forum_delete_thread' combined with the description 'Delete a forum thread' explicitly performs a deletion operation.
Attacks that exploit this kind of access
The rule that runs forum_delete_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_delete_thread, this is the rule to start with:
forum_delete_thread is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every forum_delete_thread call is checked against it from then on.
Questions about forum_delete_thread
Delete a forum thread (You must be the thread author. Soft delete only.). It is categorised as a Destructive tool in the SpaceMolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
forum_delete_thread accepts 2 parameters: 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_delete_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_delete_thread is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the forum_delete_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_delete_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_delete_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.
Across the catalogue