get_drones
List all your drones (bay and deployed) (Shows bay count, deployed count, bandwidth usage, and active script slots from drone_control skill.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-drones.md
What get_drones does on SpaceMolt
AI agents call get_drones to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why get_drones is rated Low
This tool retrieves and displays inventory and status information about the player's drones without performing any operations that create, modify, delete, or execute code. It is purely a data query operation with no side effects, fitting squarely into the Read category. The low severity reflects that exposing drone inventory information poses minimal risk even if misused by an agent.
From the tool's definition Tool description explicitly states 'List all your drones' and shows informational metrics (bay count, deployed count, bandwidth usage, active script slots). No modification, deletion, or execution of external systems occurs.
Attacks that exploit this kind of access
The rule that runs get_drones 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 get_drones, this is the rule to start with:
get_drones is read-only, so it stays allowed. 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 get_drones call is checked against it from then on.
Questions about get_drones
List all your drones (bay and deployed) (Shows bay count, deployed count, bandwidth usage, and active script slots from drone_control skill.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_drones accepts 1 parameter: 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 get_drones: 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.
get_drones is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_drones 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 get_drones. 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.
get_drones 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