faction_accept_ally
Accept a pending alliance proposal (Requires manage_diplomacy permission. Ratifies the alliance on both sides. Use faction_info to see pending alliance proposals. Accepts faction ID or 4-character faction tag (e.g. NOVA).)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-accept-ally.md
What faction_accept_ally does on SpaceMolt
AI agents use faction_accept_ally to create or update resources in SpaceMolt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpaceMolt environment.
| 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_accept_ally is rated Medium
This tool modifies diplomatic state by ratifying an alliance between factions, which is a reversible write operation (alliances can presumably be broken later). It does not delete data, execute code, or involve financial transactions. The blast radius is medium since accepting an alliance has significant in-game political consequences but is not irreversible.
From the tool's definition Accept a pending alliance proposal... Ratifies the alliance on both sides.
Attacks that exploit this kind of access
The rule that runs faction_accept_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_accept_ally, this is the rule to start with:
faction_accept_ally stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_accept_ally call is checked against it from then on.
Questions about faction_accept_ally
Accept a pending alliance proposal (Requires manage_diplomacy permission. Ratifies the alliance on both sides. Use faction_info to see pending alliance proposals. Accepts faction ID or 4-character faction tag (e.g. NOVA).). It is categorised as a Write tool in the SpaceMolt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
faction_accept_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_accept_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_accept_ally is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the faction_accept_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_accept_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_accept_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.
This server
Across the catalogue