faction_accept_invite
Accept a faction invitation (alias for join_faction) (Alias for join_faction. You must have a pending invite from the faction. Both names accept the same payload and produce the same result.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-accept-invite.md
What faction_accept_invite does on SpaceMolt
AI agents use faction_accept_invite 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 |
|---|---|---|---|
faction_id | string | Yes | UUID of faction to join (must have pending invite) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why faction_accept_invite is rated Medium
This is a reversible state modification (the agent can presumably leave a faction later), making it Write rather than Execute. It doesn't retrieve data (Read), doesn't run arbitrary code (Execute), doesn't permanently delete data (Destructive), and doesn't involve financial transactions (Financial).
From the tool's definition Tool accepts a faction invitation, which modifies the agent's faction membership status. Description states it 'accept[s] a faction invitation' and produces a result that changes game state by joining a faction.
Attacks that exploit this kind of access
The rule that runs faction_accept_invite 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_invite, this is the rule to start with:
faction_accept_invite 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_invite call is checked against it from then on.
Questions about faction_accept_invite
Accept a faction invitation (alias for join_faction) (Alias for join_faction. You must have a pending invite from the faction. Both names accept the same payload and produce the same result.). 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_invite accepts 2 parameters: faction_id, session_id. Required: faction_id, 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 faction_accept_invite: 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_invite 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_invite 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_invite. 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_invite 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