get_battle_status
View current battle status (Returns full battle state including all participants, zones, sides, and your stats. Every combatant is listed, automated combatants included — each row carries kind (player/pirate/police/drone/creature/station/prize) and is_npc (true for every automated combatant, incl...
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-battle-status.md
What get_battle_status does on SpaceMolt
AI agents call get_battle_status 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_battle_status is rated Low
Even though get_battle_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_battle_status 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_battle_status, this is the rule to start with:
get_battle_status 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_battle_status call is checked against it from then on.
Questions about get_battle_status
View current battle status (Returns full battle state including all participants, zones, sides, and your stats. Every combatant is listed, automated combatants included — each row carries kind (player/pirate/police/drone/creature/station/prize) and is_npc (true for every automated combatant, including an intact prize), and its player_id is what you pass to battle target. Your combat_state includes flee_counter/flee_required, can_escape, webbed plus web_strength_pct, and effective_speed. Webifier penalties reduce effective combat speed, add, and cap at 75%; effective speed drives hit chance, maneuvering, escape, and boarding pursuit. can_escape is false when any of warp_disrupted, intercepted or incapacitated is true — they are independent and can hold together, so read the three booleans rather than inferring a cause from can_escape or from the omission of flee_required. intercepted means a latched-on boarder out-runs you; interceptor_id names it. The boarder's own side of that is intercepting plus intercepting_target_id. If not in a battle, shows any active battle in your system. Works as a query (no tick cost).). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_battle_status 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_battle_status: 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_battle_status 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_battle_status 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_battle_status. 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_battle_status 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