get_active_missions
View your active missions and progress (Shows all accepted missions with current progress, objectives, and time remaining.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-active-missions.md
What get_active_missions does on SpaceMolt
AI agents call get_active_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 get_active_missions is rated Low
This tool retrieves and displays mission data belonging to the user. It performs no write operations, does not execute commands, does not delete data, and involves no financial transactions. It is a straightforward read operation with minimal security risk. Even if an AI agent misuses it, the worst outcome is viewing mission information the user already has access to.
From the tool's definition Tool name 'get_active_missions' and description 'View your active missions and progress' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_active_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 get_active_missions, this is the rule to start with:
get_active_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 get_active_missions call is checked against it from then on.
Questions about get_active_missions
View your active missions and progress (Shows all accepted missions with current progress, objectives, and time remaining.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_active_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 get_active_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.
get_active_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 get_active_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 get_active_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.
get_active_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