tow_wreck
Attach a tow line to a wreck for hauling (Requires a tow rig utility module fitted. Speed is reduced while towing. Travel to a salvage yard to sell or scrap the wreck. A tow rig can only tow one thing at a time — a wreck or one of your own ships of the same or smaller class scale (see 'storage' a...
This record as markdown: /tools/io-github-statico-alt-spacemolt/tow-wreck.md
What tow_wreck does on SpaceMolt
AI agents invoke tow_wreck to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
wreck_id | string | Yes | UUID of the wreck to tow (use get_wrecks to see available wrecks) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why tow_wreck is rated High
tow_wreck triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs tow_wreck 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 tow_wreck, this is the rule to start with:
tow_wreck stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 tow_wreck call is checked against it from then on.
Questions about tow_wreck
Attach a tow line to a wreck for hauling (Requires a tow rig utility module fitted. Speed is reduced while towing. Travel to a salvage yard to sell or scrap the wreck. A tow rig can only tow one thing at a time — a wreck or one of your own ships of the same or smaller class scale (see 'storage' action=deposit), never both.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
tow_wreck accepts 2 parameters: wreck_id, session_id. Required: wreck_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 tow_wreck: 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.
tow_wreck is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tow_wreck 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 tow_wreck. 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.
tow_wreck 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