faction_remove_ally
Dissolve an alliance or clear pending alliance proposals with another faction (Requires manage_diplomacy permission. Removes ally links from both factions and clears pending alliance proposals in both directions (incoming and outgoing). Notifies the other side only when an ally link was removed. ...
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-remove-ally.md
What faction_remove_ally does on SpaceMolt
AI agents call faction_remove_ally 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 |
|---|---|---|---|
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_remove_ally is rated Critical
An AI agent that decides to call faction_remove_ally 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 faction_remove_ally 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_remove_ally, this is the rule to start with:
faction_remove_ally 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 faction_remove_ally call is checked against it from then on.
Questions about faction_remove_ally
Dissolve an alliance or clear pending alliance proposals with another faction (Requires manage_diplomacy permission. Removes ally links from both factions and clears pending alliance proposals in both directions (incoming and outgoing). Notifies the other side only when an ally link was removed. Idempotent: succeeds even if no alliance or proposals existed. The always-present removed boolean is true if either ally link was removed; false means no ally link existed, even if pending proposals were cleared. Accepts faction ID or 4-character faction tag (e.g. NOVA).). 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.
faction_remove_ally accepts 2 parameters: 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_remove_ally: 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_remove_ally 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 faction_remove_ally 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_remove_ally. 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_remove_ally 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