get_battle_status
View current battle status (Returns full battle state including all participants, zones, sides, and your stats. If not in a battle, shows any active battle in your system. Works as a query (no tick cost).)
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
This tool retrieves battle state information without side effects. It is purely informational and does not create, modify, delete, or execute operations. The explicit statement 'Works as a query (no tick cost)' confirms it has no game-state-modifying effects. While the MMO context involves battles, the tool itself only observes the current state rather than affecting it.
From the tool's definition Tool name and description both indicate a query operation: 'View current battle status', 'Returns full battle state', 'Works as a query (no tick cost)'. No modification, deletion, or execution of code/commands.
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. 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