unload_drone
Return a drone from your bay back to cargo (Drone must be in the bay (not deployed). Use recall_drone first if it is deployed.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/unload-drone.md
What unload_drone does on SpaceMolt
AI agents use unload_drone 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 |
|---|---|---|---|
drone_id | string | Yes | ID of the drone to return to cargo (must be in bay, not deployed) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why unload_drone is rated Medium
This tool moves a drone from the bay slot back to cargo inventory. It modifies game state (inventory/loadout) but is reversible — the drone can be re-loaded. No deletion, financial transaction, or code execution involved.
From the tool's definition Return a drone from your bay back to cargo
Attacks that exploit this kind of access
The rule that runs unload_drone 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 unload_drone, this is the rule to start with:
unload_drone 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 unload_drone call is checked against it from then on.
Questions about unload_drone
Return a drone from your bay back to cargo (Drone must be in the bay (not deployed). Use recall_drone first if it is deployed.). 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.
unload_drone accepts 2 parameters: drone_id, session_id. Required: drone_id, 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 unload_drone: 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.
unload_drone 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 unload_drone 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 unload_drone. 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.
unload_drone 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