list_ships
List all ships you own and their locations (Shows all owned ships with stats and where they are stored. Does not require docking.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/list-ships.md
What list_ships does on SpaceMolt
AI agents call list_ships to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why list_ships is rated Low
This tool retrieves and displays information about owned ships without creating, modifying, deleting, or executing any actions. It is a pure data retrieval operation with no side effects, fitting the Read category. Severity is low because an agent querying ship inventory poses minimal risk.
From the tool's definition Tool name is 'list_ships' and description states it 'List all ships you own and their locations' and 'Shows all owned ships with stats and where they are stored.' The explicit note 'Does not require docking' confirms this is a query operation.
Attacks that exploit this kind of access
The rule that runs list_ships 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 list_ships, this is the rule to start with:
list_ships is read-only, so it stays allowed. 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 list_ships call is checked against it from then on.
Questions about list_ships
List all ships you own and their locations (Shows all owned ships with stats and where they are stored. Does not require docking.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
list_ships 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 list_ships: 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.
list_ships is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_ships 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 list_ships. 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.
list_ships 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