accept_mission
Accept a mission from the mission board (You must be docked at the base offering the mission. Maximum 5 active missions at once. Use get_missions to see available missions and their IDs.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/accept-mission.md
What accept_mission does on SpaceMolt
AI agents use accept_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 | — | Mission ID or template ID to accept (one of mission_id/template_id required) |
session_id | string | Yes | Your session ID from login/register |
template_id | string | — | Mission template ID to accept (takes priority over mission_id) |
Parameters from the server's own tool schema.
Why accept_mission is rated Medium
Accepting a mission creates a new active commitment/record in the game state (binding the agent to up to 5 missions). This is a reversible write action (missions can presumably be abandoned via the sibling 'abandon_mission' tool), modifying the agent's mission list. It does not execute code, delete data, or involve real money.
From the tool's definition Accept a mission from the mission board
Attacks that exploit this kind of access
The rule that runs accept_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 accept_mission, this is the rule to start with:
accept_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 accept_mission call is checked against it from then on.
Questions about accept_mission
Accept a mission from the mission board (You must be docked at the base offering the mission. Maximum 5 active missions at once. Use get_missions to see available missions and their IDs.). 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.
accept_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 accept_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.
accept_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 accept_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 accept_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.
accept_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