recruit_personnel
Recruit fit crew and marines at a station personnel service (Requires docking at the relevant station services: personnel for crew and marine training for marines. Crew cost 100 credits each; marines cost 250. Recruitment draws from separate station-wide pools shared by all visitors. Requests are...
This record as markdown: /tools/io-github-statico-alt-spacemolt/recruit-personnel.md
What recruit_personnel does on SpaceMolt
AI agents call recruit_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 |
|---|---|---|---|
crew | integer | — | Fit crew to recruit into the active ship. Request crew and/or marines; at least one count must be positive. |
marines | integer | — | Fit marines to recruit into the active ship. Request crew and/or marines; at least one count must be positive. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why recruit_personnel is rated Low
Even though recruit_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.
Attacks that exploit this kind of access
The rule that runs recruit_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 recruit_personnel, this is the rule to start with:
recruit_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 recruit_personnel call is checked against it from then on.
Questions about recruit_personnel
Recruit fit crew and marines at a station personnel service (Requires docking at the relevant station services: personnel for crew and marine training for marines. Crew cost 100 credits each; marines cost 250. Recruitment draws from separate station-wide pools shared by all visitors. Requests are partially fulfilled by ship capacity, available credits, and remaining pool stock; the response reports the remaining stock.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
recruit_personnel accepts 3 parameters: crew, marines, session_id. 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 recruit_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.
recruit_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 recruit_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 recruit_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.
recruit_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