self_destruct
Destroy your own ship (Outside battle, immediately destroys your ship, creates a wreck at your location, and respawns you at your home base (or empire home). During battle this standalone command is rejected: use the battle command's self_destruct action to start the in-battle countdown. Once sta...
This record as markdown: /tools/io-github-statico-alt-spacemolt/self-destruct.md
What self_destruct does on SpaceMolt
AI agents call self_destruct 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why self_destruct is rated Critical
An AI agent that decides to call self_destruct doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from SpaceMolt is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs self_destruct 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 self_destruct, this is the rule to start with:
self_destruct 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 self_destruct call is checked against it from then on.
Questions about self_destruct
Destroy your own ship (Outside battle, immediately destroys your ship, creates a wreck at your location, and respawns you at your home base (or empire home). During battle this standalone command is rejected: use the battle command's self_destruct action to start the in-battle countdown. Once started, that countdown advances automatically each battle tick; duplicate starts do not reset or extend it. Useful if you're stranded (out of fuel) or want to deny loot to attackers.). 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.
self_destruct accepts 1 parameter: session_id. 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 self_destruct: 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.
self_destruct 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 self_destruct 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 self_destruct. 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.
self_destruct 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