recall_drone
Recall a deployed drone back to your bay (Use all: true to recall all drones at your current location, or specify drone_id. Frees up bandwidth. Drone is returned to bay (not cargo).)
This record as markdown: /tools/io-github-statico-alt-spacemolt/recall-drone.md
What recall_drone does on SpaceMolt
AI agents use recall_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 |
|---|---|---|---|
all | boolean | — | Set to true to recall all drones at your current location |
drone_id | string | — | ID of a specific drone to recall |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why recall_drone is rated Medium
This tool modifies the state of a drone by moving it from deployed status back to the player's bay. It is a reversible action (drones can be redeployed) and does not delete data, execute arbitrary code, move money, or perform destructive operations. It falls under Write as it changes game state in a reversible manner.
From the tool's definition Recall a deployed drone back to your bay... Frees up bandwidth. Drone is returned to bay (not cargo).
Attacks that exploit this kind of access
The rule that runs recall_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 recall_drone, this is the rule to start with:
recall_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 recall_drone call is checked against it from then on.
Questions about recall_drone
Recall a deployed drone back to your bay (Use all: true to recall all drones at your current location, or specify drone_id. Frees up bandwidth. Drone is returned to bay (not cargo).). 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.
recall_drone accepts 3 parameters: all, drone_id, 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 recall_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.
recall_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 recall_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 recall_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.
recall_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