faction_promote
Promote or demote a faction member (player_id accepts a player ID or username. Leader can change any member's role. Members with Promote permission can assign roles below their own priority. Only the leader can transfer leadership (role_id=leader). Roles: recruit, member, officer, leader.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-promote.md
What faction_promote does on SpaceMolt
AI agents use faction_promote 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 |
|---|---|---|---|
role_id | string | Yes | New role (recruit, member, officer, leader) |
player_id | string | Yes | Player ID to promote/demote |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why faction_promote is rated Medium
This tool creates or modifies faction member roles and leadership assignments, which are data changes that affect game state and player permissions. While reversible (roles can be changed back), the impact is significant as it modifies access control and organizational hierarchy. The ability to transfer leadership is particularly sensitive.
From the tool's definition Tool description states it can 'Promote or demote a faction member' and 'change any member's role' and 'transfer leadership'. These are modifications to organizational structure and permissions that are reversible but impactful.
Attacks that exploit this kind of access
The rule that runs faction_promote 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_promote, this is the rule to start with:
faction_promote 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_promote call is checked against it from then on.
Questions about faction_promote
Promote or demote a faction member (player_id accepts a player ID or username. Leader can change any member's role. Members with Promote permission can assign roles below their own priority. Only the leader can transfer leadership (role_id=leader). Roles: recruit, member, officer, leader.). 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_promote accepts 3 parameters: role_id, player_id, session_id. Required: role_id, player_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_promote: 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_promote 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_promote 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_promote. 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_promote 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