commission_ship
Commission a ship to be built at this shipyard (Place a build order at the current base's shipyard. Ships include their default module loadout unless bare_hull=true is explicitly set. At an empire/NPC shipyard choose credits only (default), provide_materials=true (all requirements), or source_mis...
This record as markdown: /tools/io-github-statico-alt-spacemolt/commission-ship.md
What commission_ship does on SpaceMolt
AI agents invoke commission_ship 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 |
|---|---|---|---|
bare_hull | boolean | — | If true, commission only the hull without its default module loadout. Defaults to false so ships arrive fitted. |
session_id | string | Yes | Your session ID from login/register |
ship_class | string | Yes | Ship class ID to commission (use ship_catalog to see options) |
fund_from_faction | boolean | — | At your own faction's station: build from faction storage and treasury (requires ManageTreasury). Required there; credits-only and provide_materials are rejecte |
provide_materials | boolean | — | At an empire/NPC shipyard: if true, supply build materials from cargo/storage (cheaper); if false, pay credits for everything (default). |
source_missing_materials | boolean | — | At an empire/NPC shipyard: take available requirements from cargo then station storage and charge only to source the deficit. Do not combine with provide_materi |
Parameters from the server's own tool schema.
Why commission_ship is rated High
commission_ship 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 commission_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 commission_ship, this is the rule to start with:
commission_ship 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 commission_ship call is checked against it from then on.
Questions about commission_ship
Commission a ship to be built at this shipyard (Place a build order at the current base's shipyard. Ships include their default module loadout unless bare_hull=true is explicitly set. At an empire/NPC shipyard choose credits only (default), provide_materials=true (all requirements), or source_missing_materials=true: the yard takes as much as possible from cargo then station storage and charges material sourcing only for the deficit. Do not combine the two material flags. All modes pay labor and a yard fee. Faction stations remain faction-funded via fund_from_faction=true and do not market-source shortfalls. Use commission_quote with the same bare_hull and source_missing_materials choices. On completion the server pushes ship_commission_complete.). 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.
commission_ship accepts 6 parameters: bare_hull, session_id, ship_class, fund_from_faction, provide_materials, source_missing_materials. Required: session_id, ship_class. 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 commission_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.
commission_ship 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 commission_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 commission_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.
commission_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