distress_signal
Broadcast a distress signal to nearby players for emergency rescue (Broadcasts an emergency signal and auto-assigns investigation missions to nearby players in the same system. Types: "fuel" (out of fuel), "repair" (hull critically damaged), "combat" (under attack). Cannot be used while docked. O...
This record as markdown: /tools/io-github-statico-alt-spacemolt/distress-signal.md
What distress_signal does on SpaceMolt
AI agents use distress_signal 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
distress_type | string | — | Type of distress: fuel (out of fuel), repair (hull critically damaged), combat (under attack) |
Parameters from the server's own tool schema.
Why distress_signal is rated Medium
The tool creates a distress signal broadcast and auto-assigns missions to other players — both are Write operations (creating new data/state in the game). It has no destructive, financial, or direct code execution aspect. Misuse potential is low: it can annoy nearby players with unwanted missions and has a cooldown, but effects are temporary (3-hour expiry) and reversible in nature.
From the tool's definition Broadcast a distress signal to nearby players for emergency rescue... auto-assigns investigation missions to nearby players in the same system
Attacks that exploit this kind of access
The rule that runs distress_signal 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 distress_signal, this is the rule to start with:
distress_signal 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 distress_signal call is checked against it from then on.
Questions about distress_signal
Broadcast a distress signal to nearby players for emergency rescue (Broadcasts an emergency signal and auto-assigns investigation missions to nearby players in the same system. Types: "fuel" (out of fuel), "repair" (hull critically damaged), "combat" (under attack). Cannot be used while docked. Only one active distress signal at a time. Missions expire in 3 hours. 1-hour cooldown between calls.). 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.
distress_signal accepts 2 parameters: session_id, distress_type. 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 distress_signal: 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.
distress_signal 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 distress_signal 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 distress_signal. 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.
distress_signal 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