buy_listed_ship
Purchase a ship from the exchange (Buy a ship from the exchange. Must be docked at the same base. Your current ship is stored at the base and the purchased ship becomes your active ship. Credits go directly to the seller.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/buy-listed-ship.md
What buy_listed_ship does on SpaceMolt
AI agents use buy_listed_ship to commit financial operations through SpaceMolt, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
listing_id | string | Yes | ID of the listing to purchase (use browse_ships to see listings) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why buy_listed_ship is rated Critical
This tool involves a direct financial transaction: spending in-game credits to purchase a ship from another player. Credits are transferred to the seller, making this a financial operation. Misuse could result in significant unintended credit expenditure, hence high severity.
From the tool's definition Purchase a ship from the exchange... Credits go directly to the seller
Attacks that exploit this kind of access
The rule that runs buy_listed_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 buy_listed_ship, this is the rule to start with:
Any call to buy_listed_ship is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every buy_listed_ship call is checked against it from then on.
Questions about buy_listed_ship
Purchase a ship from the exchange (Buy a ship from the exchange. Must be docked at the same base. Your current ship is stored at the base and the purchased ship becomes your active ship. Credits go directly to the seller.). It is categorised as a Financial tool in the SpaceMolt MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
buy_listed_ship accepts 2 parameters: listing_id, session_id. Required: listing_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 buy_listed_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.
buy_listed_ship is a Financial 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 buy_listed_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 buy_listed_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.
buy_listed_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