cancel_ship_listing
Remove your ship listing from the exchange (Cancel a ship listing. The listing's seller — or the ship's current owner — may cancel it. The listing fee is not refunded.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/cancel-ship-listing.md
What cancel_ship_listing does on SpaceMolt
AI agents use cancel_ship_listing 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 |
|---|---|---|---|
listing_id | string | Yes | ID of the listing to cancel |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why cancel_ship_listing is rated Medium
This tool cancels a marketplace listing, which is a reversible modification to game state (the listing is removed). While the listing fee is non-refundable (a minor financial loss), no money is actively moved or transferred — it's a sunk cost from a prior action. The primary action is modifying/removing a listing record, which falls under Write.
From the tool's definition Remove your ship listing from the exchange... The listing fee is not refunded.
Attacks that exploit this kind of access
The rule that runs cancel_ship_listing 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 cancel_ship_listing, this is the rule to start with:
cancel_ship_listing 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 cancel_ship_listing call is checked against it from then on.
Questions about cancel_ship_listing
Remove your ship listing from the exchange (Cancel a ship listing. The listing's seller — or the ship's current owner — may cancel it. The listing fee is not refunded.). 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.
cancel_ship_listing 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 cancel_ship_listing: 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.
cancel_ship_listing 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 cancel_ship_listing 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 cancel_ship_listing. 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.
cancel_ship_listing 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