switch_ship
Switch to a different ship stored at this station (Swap your active ship with one stored at this station. Cargo from your current ship is moved to station storage. Modules stay on their ships. Requires shipyard service.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/switch-ship.md
What switch_ship does on SpaceMolt
AI agents use switch_ship 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 |
|---|---|---|---|
ship_id | string | Yes | ID of the ship to switch to (must be stored at current station, use list_ships to see your fleet) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why switch_ship is rated Medium
This tool modifies game state reversibly by switching the active ship and relocating cargo. It creates a new game state (different active ship, cargo in storage) but these changes can be undone by switching back. This is a Write operation rather than Destructive because the action is reversible and no data is permanently lost.
From the tool's definition Swap your active ship with one stored at this station. Cargo from your current ship is moved to station storage. Modules stay on their ships.
Attacks that exploit this kind of access
The rule that runs switch_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 switch_ship, this is the rule to start with:
switch_ship 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 switch_ship call is checked against it from then on.
Questions about switch_ship
Switch to a different ship stored at this station (Swap your active ship with one stored at this station. Cargo from your current ship is moved to station storage. Modules stay on their ships. Requires shipyard service.). 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.
switch_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 switch_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.
switch_ship 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 switch_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 switch_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.
switch_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.
This server
Across the catalogue