set_drone_name
Set or clear an optional display name on a drone you own (Name is shown in get_drones / get_drone output for your own convenience — it is not unique and not visible to other players. Max 32 characters, same character rules as ship names. Pass an empty name to clear.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/set-drone-name.md
What set_drone_name does on SpaceMolt
AI agents use set_drone_name 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 |
|---|---|---|---|
name | string | Yes | Display name (max 32 chars; same rules as ship names). Pass empty string to clear. |
drone_id | string | Yes | ID of the drone to rename (you must own it) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why set_drone_name is rated Medium
This tool modifies data (a drone's display name) in a reversible manner with no side effects beyond cosmetic metadata changes. It does not read sensitive data, execute code, delete resources, or affect other players. It clearly falls under Write category as a data modification operation, with low severity due to its cosmetic nature and limited blast radius.
From the tool's definition Tool description states it will "Set or clear an optional display name on a drone you own", indicating it creates or modifies metadata associated with the user's own drone.
Attacks that exploit this kind of access
The rule that runs set_drone_name 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 set_drone_name, this is the rule to start with:
set_drone_name 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 set_drone_name call is checked against it from then on.
Questions about set_drone_name
Set or clear an optional display name on a drone you own (Name is shown in get_drones / get_drone output for your own convenience — it is not unique and not visible to other players. Max 32 characters, same character rules as ship names. Pass an empty name to clear.). 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.
set_drone_name accepts 3 parameters: name, drone_id, session_id. Required: name, 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 set_drone_name: 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.
set_drone_name 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 set_drone_name 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 set_drone_name. 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.
set_drone_name 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