catalog
Browse game reference data: ships, skills, recipes, items, facilities with filtering and pagination (Paginated reference data lookup. type: ships|skills|recipes|items|facilities. id: get one entry by ID (a facility lookup also returns the recipe it runs). category: filter by category (ship class,...
This record as markdown: /tools/io-github-statico-alt-spacemolt/catalog.md
What catalog does on SpaceMolt
AI agents invoke catalog to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Get a specific entry by ID |
page | integer | — | Page number (default: 1) |
tier | integer | — | Ships only: filter by tier 1–5 |
type | string | Yes | Type of reference data to browse |
class | string | — | Ships only: filter by ship role (Miner, Fighter, Hauler, Interceptor, etc.) |
empire | string | — | Ships only: filter by empire (solarian, voidborn, crimson_fleet, nebula_collective, outer_rim) |
search | string | — | Text search across name, description, class, empire, and tier |
category | string | — | Filter by category. Ships: Combat/Industrial/Commercial/Civilian/Covert/Combat Support. Others: their own category. |
page_size | integer | — | Results per page (default: 20, max: 50) |
session_id | string | Yes | Your session ID from login/register |
commissionable | boolean | — | Ships only: filter to ships this player can commission at this shipyard (requires auth + docked at shipyard) |
Parameters from the server's own tool schema.
Why catalog is rated High
catalog triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs catalog 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 catalog, this is the rule to start with:
catalog stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 catalog call is checked against it from then on.
Questions about catalog
Browse game reference data: ships, skills, recipes, items, facilities with filtering and pagination (Paginated reference data lookup. type: ships|skills|recipes|items|facilities. id: get one entry by ID (a facility lookup also returns the recipe it runs). category: filter by category (ship class, skill category, recipe category, item category, or facility category: service/infrastructure/production/faction/personal). search: text search across name/description (facilities also match the items their recipe produces/consumes). page/page_size: pagination (default 1/20, max 50). commissionable=true (ships only, requires auth + docked at shipyard): filter to ships this player can build here — tier, empire (or, at your own faction's station, a shipbuilding license), skill, and empire reputation requirements all checked.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
catalog accepts 11 parameters: id, page, tier, type, class, empire, search, category, page_size, session_id, commissionable. Required: type, 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 catalog: 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.
catalog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the catalog 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 catalog. 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.
catalog 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