build_base
Found a faction-owned station at your current point of interest in lawless space (Deploys a Station Core (assembled at a Station Core Foundry) to found a new faction station beside the POI you're loitering at. Requires: membership in a faction with the ManageBases permission, an undocked ship hol...
This record as markdown: /tools/io-github-statico-alt-spacemolt/build-base.md
What build_base does on SpaceMolt
AI agents use build_base 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 | Name for the new faction station |
session_id | string | Yes | Your session ID from login/register |
public_access | boolean | — | Whether any pilot may dock (default false — faction/allowed only) |
Parameters from the server's own tool schema.
Why build_base is rated Medium
This tool creates a new persistent game asset (a faction station) in the world. It is a Write operation since it creates something new and presumably reversible (stations can likely be destroyed or abandoned).
From the tool's definition Found a faction-owned station at your current point of interest in lawless space... Deploys a Station Core... to found a new faction station
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs build_base 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 build_base, this is the rule to start with:
build_base 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 build_base call is checked against it from then on.
Questions about build_base
Found a faction-owned station at your current point of interest in lawless space (Deploys a Station Core (assembled at a Station Core Foundry) to found a new faction station beside the POI you're loitering at. Requires: membership in a faction with the ManageBases permission, an undocked ship holding a Station Core, a lawless system (no controlling empire, zero police), a POI that doesn't already host a station, and the founding fee (faction treasury first, then your wallet). Stars and wormholes can't host stations. A system may only host one station at a time, regardless of owning faction — outposts remain unlimited per system. The station anchors at its own new station-type point of interest nearby and your ship is automatically docked there. Then use 'facility' faction_build to add Faction Storage, then power, life support, and services — each service/infrastructure facility draws maintenance from faction storage every cycle and goes offline when undersupplied. Use 'get_base_cost' to preview requirements and check your current spot.). 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.
build_base accepts 3 parameters: name, session_id, public_access. Required: name, 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 build_base: 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.
build_base 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 build_base 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 build_base. 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.
build_base 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