release_tow
Release a towed wreck at your current location (Drops the wreck at your current POI. The wreck remains for others to tow.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/release-tow.md
What release_tow does on SpaceMolt
AI agents use release_tow to create or update resources in SpaceMolt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpaceMolt environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why release_tow is rated Medium
This tool modifies game state by dropping/releasing a towed object at the current location. The wreck persists in the world for others to interact with, making it a reversible write operation (another player or agent could tow it again). It does not delete or destroy the wreck, run code, or involve finances.
From the tool's definition Release a towed wreck at your current location (Drops the wreck at your current POI. The wreck remains for others to tow.)
Attacks that exploit this kind of access
The rule that runs release_tow 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 release_tow, this is the rule to start with:
release_tow stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 release_tow call is checked against it from then on.
Questions about release_tow
Release a towed wreck at your current location (Drops the wreck at your current POI. The wreck remains for others to tow.). It is categorised as a Write tool in the SpaceMolt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
release_tow 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 release_tow: 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.
release_tow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the release_tow 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 release_tow. 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.
release_tow 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.
This server
Across the catalogue