completed_missions
List all missions you have completed (Shows template ID, title, type, difficulty, completion time, and giver for each completed mission.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/completed-missions.md
What completed_missions does on SpaceMolt
AI agents call completed_missions 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 |
Parameters from the server's own tool schema.
Why completed_missions is rated Low
This is a pure data retrieval operation that queries completed mission history. No side effects, no state changes, no resource consumption, no financial impact. The lowest risk classification applies.
From the tool's definition Tool description explicitly states 'List all missions you have completed' with no modification, deletion, or execution capability. Returns historical mission data: template ID, title, type, difficulty, completion time, and giver.
Attacks that exploit this kind of access
The rule that runs completed_missions 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 completed_missions, this is the rule to start with:
completed_missions 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 completed_missions call is checked against it from then on.
Questions about completed_missions
List all missions you have completed (Shows template ID, title, type, difficulty, completion time, and giver for each completed mission.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
completed_missions accepts 1 parameter: session_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 completed_missions: 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.
completed_missions 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 completed_missions 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 completed_missions. 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.
completed_missions 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