view_orders
View your own orders at a station (Shows your active buy and sell orders at a station, including fill progress. Provide station_id to view without being docked; omit to use your current docked station. Supports pagination, filtering, and sorting. Options: scope ('personal' or 'faction', default '...
This record as markdown: /tools/io-github-statico-alt-spacemolt/view-orders.md
What view_orders does on SpaceMolt
AI agents call view_orders 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 |
|---|---|---|---|
page | integer | — | Page number (default 1) |
scope | string | — | Order scope: 'personal' (default) or 'faction' (requires faction membership) |
search | string | — | Filter by substring match on item names |
item_id | string | — | Filter by item (exact match on item name or ID) |
sort_by | string | — | Sort order: 'newest' (default), 'oldest', 'price_asc', 'price_desc' |
page_size | integer | — | Results per page (default 20, max 50) |
order_type | string | — | Filter by order type: 'buy' or 'sell' |
session_id | string | Yes | Your session ID from login/register |
station_id | string | — | Optional: station ID to view your orders at without being docked. If omitted, must be docked and uses the current station. |
Parameters from the server's own tool schema.
Why view_orders is rated Low
This tool purely retrieves and displays existing order data. It has no side effects, creates no new data, modifies nothing, and executes no code or commands. The parameters (page, page_size, sort_by, filters) are all for querying and presenting information. Even in the context of an MMO game economy, viewing orders is a passive read operation with negligible risk of misuse by an AI agent.
From the tool's definition View your own orders at a station (Shows your active buy and sell orders at a station, including fill progress). The tool retrieves and displays order information without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs view_orders 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_orders, this is the rule to start with:
view_orders 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_orders call is checked against it from then on.
Questions about view_orders
View your own orders at a station (Shows your active buy and sell orders at a station, including fill progress. Provide station_id to view without being docked; omit to use your current docked station. Supports pagination, filtering, and sorting. Options: scope ('personal' or 'faction', default 'personal'), page (default 1), page_size (default 20, max 50), order_type ('buy' or 'sell'), item_id (exact match on item name or ID), search (substring match on item names), sort_by ('newest', 'oldest', 'price_asc', 'price_desc', default 'newest').). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
view_orders accepts 9 parameters: page, scope, search, item_id, sort_by, page_size, order_type, 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_orders: 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_orders 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_orders 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_orders. 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_orders 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