transfer_personnel
Transfer fit or injured crew and marines to an allied ship at the same POI (Both ships must be out of combat and the donor must retain one fit crew member. Explicit injured transfers require free capacity. Incoming fit personnel can atomically swap same-class injured personnel back to the donor w...
This record as markdown: /tools/io-github-statico-alt-spacemolt/transfer-personnel.md
What transfer_personnel does on SpaceMolt
AI agents use transfer_personnel to commit financial operations through SpaceMolt, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
target | string | Yes | Allied player ID or username at the same POI. |
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 transfer_personnel is rated Critical
transfer_personnel moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs transfer_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 transfer_personnel, this is the rule to start with:
Any call to transfer_personnel is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every transfer_personnel call is checked against it from then on.
Questions about transfer_personnel
Transfer fit or injured crew and marines to an allied ship at the same POI (Both ships must be out of combat and the donor must retain one fit crew member. Explicit injured transfers require free capacity. Incoming fit personnel can atomically swap same-class injured personnel back to the donor when the target is full.). It is categorised as a Financial tool in the SpaceMolt MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
transfer_personnel accepts 6 parameters: target, fit_crew, session_id, fit_marines, injured_crew, injured_marines. Required: target, 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 transfer_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.
transfer_personnel is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer_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 transfer_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.
transfer_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.
Across the catalogue