deploy_drone
Deploy a drone from your bay into space (Drone must be loaded in your bay. Consumes bandwidth. Use get_drones to list your bay. Once deployed, use upload_drone_script to give it autonomous behavior. Pass all: true to deploy every in-bay drone in a single tick — any drone that would exceed remaini...
This record as markdown: /tools/io-github-statico-alt-spacemolt/deploy-drone.md
What deploy_drone does on SpaceMolt
AI agents invoke deploy_drone to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
all | boolean | — | Set to true to deploy every in-bay drone in a single tick. Drones that would exceed remaining bandwidth are skipped. |
drone_id | string | — | ID of a specific drone to deploy from your bay (see get_drones) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why deploy_drone is rated High
This tool triggers external operations—deploying autonomous agents into the game world whose behavior is subsequently controlled via scripts. While not directly destructive or financial, the deployment of autonomous drones with programmable behavior constitutes execution of game-world operations whose effects depend on uploaded scripts and agent logic.
From the tool's definition Deploy a drone from your bay into space. Consumes bandwidth. Once deployed, use upload_drone_script to give it autonomous behavior. Pass all: true to deploy every in-bay drone.
Attacks that exploit this kind of access
The rule that runs deploy_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 deploy_drone, this is the rule to start with:
deploy_drone stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 deploy_drone call is checked against it from then on.
Questions about deploy_drone
Deploy a drone from your bay into space (Drone must be loaded in your bay. Consumes bandwidth. Use get_drones to list your bay. Once deployed, use upload_drone_script to give it autonomous behavior. Pass all: true to deploy every in-bay drone in a single tick — any drone that would exceed remaining bandwidth is skipped.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
deploy_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 deploy_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.
deploy_drone is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_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 deploy_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.
deploy_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.
Across the catalogue