decline_mission
Decline a mission and hear the NPC's response (Returns the mission giver's decline dialog. The mission remains available — you can still accept it later. Must be docked at a base where the mission is available.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/decline-mission.md
What decline_mission does on SpaceMolt
AI agents call decline_mission as a supporting operation in SpaceMolt workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
mission_id | string | — | Mission ID to decline (alias for template_id) |
session_id | string | Yes | Your session ID from login/register |
template_id | string | — | Mission template ID to decline (one of template_id/mission_id required) |
Parameters from the server's own tool schema.
Why decline_mission is rated Low
This tool only declines/dismisses a mission offer and returns dialog text. No data is deleted, modified, or created; no real-world financial or destructive action occurs. The mission remains available, so the action is fully reversible. This is closer to a read/interaction with no lasting side effects, best classified as Other.
From the tool's definition 'The mission remains available — you can still accept it later' and 'Decline a mission and hear the NPC's response'
Attacks that exploit this kind of access
The rule that runs decline_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 decline_mission, this is the rule to start with:
decline_mission gets a rate cap, and 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 decline_mission call is checked against it from then on.
Questions about decline_mission
Decline a mission and hear the NPC's response (Returns the mission giver's decline dialog. The mission remains available — you can still accept it later. Must be docked at a base where the mission is available.). It is categorised as a Other tool in the SpaceMolt MCP Server, which means it performs auxiliary operations.
decline_mission accepts 3 parameters: mission_id, session_id, template_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 decline_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.
decline_mission is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the decline_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 decline_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.
decline_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