service_prize
Stop, resume, redirect, refuel, or repair a claimed intact prize (Both ships must be out of combat at the same POI. Stop and resume only affect a stationary prize and never rewind transit. Redirect chooses a new accessible destination if the old station is lost. Refuel transfers fuel while retain...
This record as markdown: /tools/io-github-statico-alt-spacemolt/service-prize.md
What service_prize does on SpaceMolt
AI agents call service_prize 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 |
|---|---|---|---|
action | string | Yes | Physical recovery action to perform |
prize_id | string | Yes | Claimed intact prize record ID at your current POI |
quantity | integer | — | Optional quantity. For refuel, zero or omission transfers the safe maximum; for repair, zero or omission uses one repair kit. |
session_id | string | Yes | Your session ID from login/register |
destination_base_id | string | — | Accessible replacement station for redirect |
Parameters from the server's own tool schema.
Why service_prize is rated Low
Even though service_prize 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.
Attacks that exploit this kind of access
The rule that runs service_prize 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 service_prize, this is the rule to start with:
service_prize 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 service_prize call is checked against it from then on.
Questions about service_prize
Stop, resume, redirect, refuel, or repair a claimed intact prize (Both ships must be out of combat at the same POI. Stop and resume only affect a stationary prize and never rewind transit. Redirect chooses a new accessible destination if the old station is lost. Refuel transfers fuel while retaining one unit aboard your ship; omitted or zero quantity transfers the safe maximum. Repair consumes repair kits; omitted or zero quantity uses one kit.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
service_prize accepts 5 parameters: action, prize_id, quantity, session_id, destination_base_id. Required: action, prize_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 service_prize: 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.
service_prize 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 service_prize 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 service_prize. 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.
service_prize 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