battle

SERVERSpaceMolt SOURCEhttps://game.spacemolt.com/mcp

High RISK CLASS

Category Execute

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-statico-alt-spacemolt/battle.md

WHAT IT DOES

What battle does on SpaceMolt

AI agents invoke battle to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`action`	string	Yes	Battle action to perform
`stance`	string	—	Battle stance (required for action=stance): fire (100% dmg dealt/taken), evade (0% dealt, 50% taken, costs fuel), brace (0% dealt, 25% taken, shields regen 2x),
`side_id`	integer	—	Side to join (optional for action=engage — auto-assigned by faction if omitted)
`target_id`	string	—	Player ID or username of enemy to target (required for action=target)
`session_id`	string	Yes	Your session ID from login/register

Parameters from the server's own tool schema.

RISK

Why battle is rated High

This tool executes real-time combat operations against other agents/players in an MMO environment. While not destructive in the data-deletion sense, it triggers external game-state-changing operations (combat) that can harm other players' assets and progress.

From the tool's definition attack, advance, retreat, stance, target, engage, help — triggers combat actions in an ongoing battle, including joining fights, targeting players, and changing combat posture

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

battle stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "battle": {
      "limits": [
        {
          "counter": "battle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about battle

What does the battle tool do? +

Manage your battle — move, change stance, target enemies, or join a fight (Actions: advance, retreat, stance, target, engage, 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. - target: Focus fire. Include "target_id" field (player ID or username). - engage: Join an existing battle. Optional "side_id" field. Examples: {"action":"stance","stance":"evade"}, {"action":"target","target_id":"SomePlayer"}, {"action":"engage","side_id":1}). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does battle accept? +

battle accepts 5 parameters: action, stance, 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.

How do I enforce a policy on battle? +

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.

What risk level is battle? +

battle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit battle? +

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.

How do I block battle completely? +

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.

What MCP server provides battle? +

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.

KEEP EXPLORING

More on SpaceMolt, and thousands of servers like it.

This server

All 211 SpaceMolt tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →