faction_create_role
Create a custom faction role (Requires manage_roles permission. Priority 2-99 (default roles: recruit=1, member=10, officer=50, leader=100). Your priority must exceed the new role's priority.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-create-role.md
What faction_create_role does on SpaceMolt
AI agents use faction_create_role 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 |
|---|---|---|---|
name | string | Yes | Role name |
priority | integer | Yes | Role priority (2-99). Default roles: recruit=1, member=10, officer=50, leader=100 |
session_id | string | Yes | Your session ID from login/register |
permissions | object | — | Permission flags (invite, kick, manage_roles, manage_treasury, etc.) |
Parameters from the server's own tool schema.
Why faction_create_role is rated Medium
This tool creates new faction roles within the game's permission system. The action is reversible (roles can presumably be deleted or modified), affects game state in a bounded way (faction governance), and has no financial consequences or irreversible destructive impact.
From the tool's definition Tool name 'faction_create_role' and description 'Create a custom faction role' indicates data creation. The permission check ('Requires `manage_roles` permission') and priority hierarchy constraints are reversible governance modifications typical of Write…
Attacks that exploit this kind of access
The rule that runs faction_create_role 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_create_role, this is the rule to start with:
faction_create_role 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_create_role call is checked against it from then on.
Questions about faction_create_role
Create a custom faction role (Requires manage_roles permission. Priority 2-99 (default roles: recruit=1, member=10, officer=50, leader=100). Your priority must exceed the new role's priority.). 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_create_role accepts 4 parameters: name, priority, session_id, permissions. Required: name, priority, 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_create_role: 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_create_role 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_create_role 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_create_role. 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_create_role 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