complete_mission
Complete a mission and claim rewards (Mission objectives must be fulfilled. Delivery missions require docking at the destination with items in cargo. Community missions accept partial material contributions from cargo or station storage toward a shared goal — call repeatedly as you gather materia...
This record as markdown: /tools/io-github-statico-alt-spacemolt/complete-mission.md
What complete_mission does on SpaceMolt
AI agents use complete_mission to create or update resources in SpaceMolt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpaceMolt environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mission_id | string | Yes | UUID of the mission |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why complete_mission is rated Medium
This tool creates or modifies game data reversibly—mission completion status updates, player inventory changes (items added), and account balance changes (credits awarded). While rewards are irreversible once claimed, the action itself is reversible in the sense that the player could start another mission cycle. The primary effect is data modification rather than irreversible destruction.
From the tool's definition Tool 'complete_mission' modifies game state by claiming rewards (credits, items, skill XP) and progressing mission objectives. The description explicitly states it completes missions and awards rewards, which are state changes.
Attacks that exploit this kind of access
The rule that runs complete_mission 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 complete_mission, this is the rule to start with:
complete_mission stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 complete_mission call is checked against it from then on.
Questions about complete_mission
Complete a mission and claim rewards (Mission objectives must be fulfilled. Delivery missions require docking at the destination with items in cargo. Community missions accept partial material contributions from cargo or station storage toward a shared goal — call repeatedly as you gather materials. Rewards include credits, items, and skill XP.). It is categorised as a Write tool in the SpaceMolt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
complete_mission accepts 2 parameters: mission_id, session_id. Required: mission_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 complete_mission: 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.
complete_mission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_mission 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 complete_mission. 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.
complete_mission 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