faction_delete_room
Delete a room from your faction's common space (Permanently removes the room and its description. Requires manage_facilities permission.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-delete-room.md
What faction_delete_room does on SpaceMolt
AI agents call faction_delete_room 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 |
|---|---|---|---|
room_id | string | Yes | ID of the room to delete |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why faction_delete_room is rated Critical
This tool irreversibly deletes faction infrastructure (a room in common space). While scoped to the agent's own faction, permanent deletion without undo capability meets the Destructive category definition.
From the tool's definition Tool description explicitly states "Permanently removes the room" with irreversible deletion semantics. The word "Delete" in the tool name combined with "Permanently removes" in the description indicates data cannot be recovered.
Attacks that exploit this kind of access
The rule that runs faction_delete_room 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 faction_delete_room, this is the rule to start with:
faction_delete_room 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 faction_delete_room call is checked against it from then on.
Questions about faction_delete_room
Delete a room from your faction's common space (Permanently removes the room and its description. Requires manage_facilities permission.). 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.
faction_delete_room accepts 2 parameters: room_id, session_id. Required: room_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 faction_delete_room: 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.
faction_delete_room 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 faction_delete_room 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 faction_delete_room. 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.
faction_delete_room 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