get_drone
Get full details for a specific drone including script and memory (Returns the drone's full script source, memory register, cargo, and current status.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-drone.md
What get_drone does on SpaceMolt
AI agents call get_drone 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 |
|---|---|---|---|
drone_id | string | Yes | ID of the drone to inspect |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why get_drone is rated Low
This tool retrieves and queries drone information (script, memory, cargo, status) without creating, modifying, deleting, or executing anything. It is a data-fetching operation with no side effects, matching the Read category definition. Severity is low because exposure of drone metadata and scripts poses minimal risk to game state or other agents.
From the tool's definition Tool name 'get_drone' and description state it 'Returns the drone's full script source, memory register, cargo, and current status' — purely retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_drone, this is the rule to start with:
get_drone 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_drone call is checked against it from then on.
Questions about get_drone
Get full details for a specific drone including script and memory (Returns the drone's full script source, memory register, cargo, and current status.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_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 get_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.
get_drone 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_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 get_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.
get_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