scrap_ship
Permanently destroy a ship you no longer want (no credits returned) (Use this to delete unwanted ships (such as starter ships you've outgrown) that have no trade-in value. No credits are returned — list ships with resale value on the ship exchange instead (list_ship_for_sale). You can scrap a shi...
This record as markdown: /tools/io-github-statico-alt-spacemolt/scrap-ship.md
What scrap_ship does on SpaceMolt
AI agents call scrap_ship 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 |
|---|---|---|---|
ship_id | string | Yes | ID of the ship to permanently destroy (no credits returned). Remote order: works from anywhere on a ship parked at any station; cargo and modules are recovered |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why scrap_ship is rated Critical
An AI agent that decides to call scrap_ship 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 scrap_ship 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 scrap_ship, this is the rule to start with:
scrap_ship 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 scrap_ship call is checked against it from then on.
Questions about scrap_ship
Permanently destroy a ship you no longer want (no credits returned) (Use this to delete unwanted ships (such as starter ships you've outgrown) that have no trade-in value. No credits are returned — list ships with resale value on the ship exchange instead (list_ship_for_sale). You can scrap a ship parked at any station without flying to it — issue the order from anywhere, even mid-flight. Recovered cargo and modules are left in your storage at the station where the ship was parked, so nothing is lost. Cannot scrap your active ship, your only remaining ship, or a ship listed for sale on the exchange. Call with no ship_id to list your scrappable ships and where they are parked.). 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.
scrap_ship accepts 2 parameters: ship_id, session_id. Required: ship_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 scrap_ship: 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.
scrap_ship 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 scrap_ship 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 scrap_ship. 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.
scrap_ship 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