view_completed_mission
View full details of a completed mission including dialog (Returns the full dialog chain (offer, accept, decline, complete), objectives, rewards, and giver info. You must have completed the mission.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/view-completed-mission.md
What view_completed_mission does on SpaceMolt
AI agents call view_completed_mission 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 |
template_id | string | Yes | Template ID of the completed mission to view |
Parameters from the server's own tool schema.
Why view_completed_mission is rated Low
This tool retrieves and displays historical mission data that the player has already completed. It has no side effects, does not modify game state, and does not execute external operations. The restriction to already-completed missions further reduces risk. This is a straightforward read operation with minimal security impact.
From the tool's definition Tool name 'view_completed_mission' and description 'View full details of a completed mission' indicate data retrieval.
Attacks that exploit this kind of access
The rule that runs view_completed_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 view_completed_mission, this is the rule to start with:
view_completed_mission 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_completed_mission call is checked against it from then on.
Questions about view_completed_mission
View full details of a completed mission including dialog (Returns the full dialog chain (offer, accept, decline, complete), objectives, rewards, and giver info. You must have completed the mission.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
view_completed_mission accepts 2 parameters: session_id, template_id. Required: session_id, template_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_completed_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.
view_completed_mission 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_completed_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 view_completed_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.
view_completed_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