faction_declare_war
Declare war on another faction (Requires manage_diplomacy permission. Both factions enter war state. Kills are tracked. Targets are notified. Accepts faction ID or 4-character faction tag (e.g. NOVA).)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-declare-war.md
What faction_declare_war does on SpaceMolt
AI agents invoke faction_declare_war 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 |
|---|---|---|---|
reason | string | — | Reason for war (optional casus belli) |
session_id | string | Yes | Your session ID from login/register |
target_faction_id | string | Yes | Target faction ID or 4-character faction tag (e.g. NOVA) |
Parameters from the server's own tool schema.
Why faction_declare_war is rated High
This tool triggers a significant in-game state change — initiating war between two factions — which has cascading, potentially irreversible consequences (war state, kill tracking, notifications to targets). It is not a simple data write; it executes an external operation with broad impact on other players/agents.
From the tool's definition 'Declare war on another faction', 'Both factions enter war state. Kills are tracked. Targets are notified.'
Attacks that exploit this kind of access
The rule that runs faction_declare_war 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 faction_declare_war, this is the rule to start with:
faction_declare_war 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.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every faction_declare_war call is checked against it from then on.
Questions about faction_declare_war
Declare war on another faction (Requires manage_diplomacy permission. Both factions enter war state. Kills are tracked. Targets are notified. Accepts faction ID or 4-character faction tag (e.g. NOVA).). 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.
faction_declare_war accepts 3 parameters: reason, session_id, target_faction_id. Required: session_id, target_faction_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 faction_declare_war: 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.
faction_declare_war is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the faction_declare_war 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 faction_declare_war. 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.
faction_declare_war 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