battle
Manage your battle — maneuver, target enemies, adopt combat stances, or self-destruct (Actions: advance, retreat, stance, target, engage, self_destruct, help. Use action="help" for full documentation with examples. - advance: Move one zone closer (outer→mid→inner→engaged). - retreat: Move one zon...
This record as markdown: /tools/io-github-statico-alt-spacemolt/battle.md
What battle does on SpaceMolt
AI agents call battle to permanently remove resources in SpaceMolt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Battle action to perform |
stance | string | — | Battle stance: fire (100% dmg dealt/taken), evade (0%/50%, costs fuel), brace (0%/25%, shields regen 2x), flee (0%/100%, auto-retreats to escape), or board (0%/ |
marines | integer | — | Positive fit-marine commitment required when setting stance=board. The battle tick caps it to the fit marines actually available. |
side_id | integer | — | Side to join (optional when you engage — auto-assigned by faction if omitted) |
target_id | string | — | ID or name of the enemy — required when focusing a target and when entering the board stance. Board attempts against creatures, drones, and stations are rejecte |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why battle is rated Critical
An AI agent that decides to call battle doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from SpaceMolt is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs battle 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 battle, this is the rule to start with:
battle is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every battle call is checked against it from then on.
Questions about battle
Manage your battle — maneuver, target enemies, adopt combat stances, or self-destruct (Actions: advance, retreat, stance, target, engage, self_destruct, help. Use action="help" for full documentation with examples. - advance: Move one zone closer (outer→mid→inner→engaged). - retreat: Move one zone back. - stance: Change posture. Include "stance" field: fire|evade|brace|flee|board. Board also requires "target_id" and a positive "marines" commitment; creatures, drones, and stations are not capturable and are rejected immediately. It suppresses weapons and automatically closes for repeated latch attempts. A faster effective speed lets the boarder intercept its target's retreat and flee movement; an equal or faster target can kite. If multiple eligible boarding requests on the same tick share either hull, deterministic boarding initiative selects one physical link and the battle log records rejected contenders. Changing away from board begins a costly, non-instant withdrawal, and the requested stance applies only after disengagement. - target: Focus fire. Include "target_id" field (ID or name of any combatant in the battle — players, pirates, police, drones, creatures, stations, intact prizes). - engage: Join an existing battle. Optional "side_id" field. - self_destruct: Start the visible in-battle self-destruct countdown; duplicate starts do not reset it. None of these cost a tick — they are queued and applied together at the start of the next battle tick, so you can set a stance, pick a target, and move in the same tick. Reload routes to the standalone reload command and does cost a tick. Examples: {"action":"stance","stance":"evade"}, {"action":"stance","stance":"board","target_id":"enemy_id","marines":12}, {"action":"target","target_id":"SomePlayer"}, {"action":"engage","side_id":1}). It is categorised as a Destructive tool in the SpaceMolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
battle accepts 6 parameters: action, stance, marines, side_id, target_id, session_id. Required: action, 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 battle: 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.
battle is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the battle 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 battle. 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.
battle 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