view_storage
View your storage at a station (Shows items and ships stored at a station. Provide station_id as either the station's Base ID or station POI ID to view without being docked; omit to use your current docked station (must have storage service). Every response carries a 'locations' array naming each...
This record as markdown: /tools/io-github-statico-alt-spacemolt/view-storage.md
What view_storage does on SpaceMolt
AI agents call view_storage 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 |
station_id | string | — | Optional: station Base ID or station POI ID to view storage at without being docked. If omitted while docked, uses the current station. If omitted while undocke |
Parameters from the server's own tool schema.
Why view_storage is rated Low
Even though view_storage only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs view_storage 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 view_storage, this is the rule to start with:
view_storage 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 view_storage call is checked against it from then on.
Questions about view_storage
View your storage at a station (Shows items and ships stored at a station. Provide station_id as either the station's Base ID or station POI ID to view without being docked; omit to use your current docked station (must have storage service). Every response carries a 'locations' array naming each station where you hold items or parked ships, with base_id, base_name, system, system_name, item_count, and ship_count. Undocked with no station_id, the command returns that summary with an empty base_id instead of a 'not_docked' error.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
view_storage accepts 2 parameters: session_id, station_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 view_storage: 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.
view_storage 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 view_storage 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 view_storage. 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.
view_storage 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