arena
Consequence-free combat at an arena POI: challenge a pilot, fight on the normal battle engine, leave with ship and crew intact (Actions: challenge, accept, decline, cancel, status, challenges, fight, help. Use action="help" for full documentation. - challenge: Challenge an undocked pilot at this ...
This record as markdown: /tools/io-github-statico-alt-spacemolt/arena.md
What arena does on SpaceMolt
AI agents call arena 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 | Arena action to perform |
player_id | string | — | Player name or ID to challenge (for 'challenge') |
session_id | string | Yes | Your session ID from login/register |
challenge_id | string | — | For 'fight': the NPC challenge to start, from 'challenges'. |
max_side_size | integer | — | For 'challenge': maximum ships per side. 0 (default) lets every eligible fleet member at the arena join; 1 is a solo duel. |
Parameters from the server's own tool schema.
Why arena is rated Critical
An AI agent that decides to call arena 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 arena 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 arena, this is the rule to start with:
arena 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 arena call is checked against it from then on.
Questions about arena
Consequence-free combat at an arena POI: challenge a pilot, fight on the normal battle engine, leave with ship and crew intact (Actions: challenge, accept, decline, cancel, status, challenges, fight, help. Use action="help" for full documentation. - challenge: Challenge an undocked pilot at this arena POI (e.g. the Blood Arena in Krynn). Include "player_id". Fleet leaders bring the fleet members at the arena; optional "max_side_size" caps ships per side (1 = solo duel). - accept/decline: Answer a pending challenge. cancel: Withdraw one you issued. status: Pending challenges, current arena battle, arena stats and today's arena XP. - challenges: List the NPC challenges (lore, arena, loadout rules, enemy lines, what each requires, your wins). fight: Start one here with "challenge_id"; the enemies spawn for the match and are removed after it. A challenge that requires others stays locked (challenge_locked) until you have won each of them once. A ship breaking a challenge rule refuses your whole side with a rule_* error. Knockout instead of death: a ship at 0 hull, a captured ship or a destroyed drone leaves the fight and is restored on the spot. Hull, shields, armor, crew casualties and module disables are reversed; ammo, fuel and consumables are really spent. Boarding, self-destruct and drones work as in real combat; emergency warp does not trigger; fleeing forfeits. Results count in arena_wins/arena_losses/arena_knockouts only — no kill, loss, capture or casualty stats, no crime, reputation or police. Combat XP is earned normally up to a daily per-skill cap.). 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.
arena accepts 5 parameters: action, player_id, session_id, challenge_id, max_side_size. 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 arena: 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.
arena 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 arena 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 arena. 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.
arena 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