faction_personnel
View, recruit, or transfer personnel held in your faction's local reserve (Requires docking at a station where your faction operates a personnel reserve. Recruit draws from the station's shared personnel pools and faction treasury and requires ManageTreasury. Deposits are available to every membe...
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-personnel.md
What faction_personnel does on SpaceMolt
AI agents call faction_personnel to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | Reserve operation; defaults to status. On v2 transports this field is named personnel_action. |
fit_crew | integer | — | |
session_id | string | Yes | Your session ID from login/register |
fit_marines | integer | — | |
injured_crew | integer | — | |
injured_marines | integer | — |
Parameters from the server's own tool schema.
Why faction_personnel is rated Low
Even though faction_personnel only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs faction_personnel 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_personnel, this is the rule to start with:
faction_personnel is read-only, so it stays allowed. 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_personnel call is checked against it from then on.
Questions about faction_personnel
View, recruit, or transfer personnel held in your faction's local reserve (Requires docking at a station where your faction operates a personnel reserve. Recruit draws from the station's shared personnel pools and faction treasury and requires ManageTreasury. Deposits are available to every member; withdrawals require ManageTreasury. Transfers require being out of combat and the active ship always retains one fit crew member.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
faction_personnel accepts 6 parameters: action, fit_crew, session_id, fit_marines, injured_crew, injured_marines. Required: 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_personnel: 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_personnel is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the faction_personnel 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_personnel. 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_personnel 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