set_home_base
Set your home base for respawning (Sets your current docked base as your home base — you will respawn there if destroyed. No payload parameters; the base you are docked at is always used.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/set-home-base.md
What set_home_base does on SpaceMolt
AI agents use set_home_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 |
|---|---|---|---|
base_id | string | Yes | UUID of base to set as home (must be docked there) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why set_home_base is rated Medium
An AI agent can call set_home_base faster than any human can review: one bad instruction and it creates or modifies resources in SpaceMolt by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs set_home_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 set_home_base, this is the rule to start with:
set_home_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 set_home_base call is checked against it from then on.
Questions about set_home_base
Set your home base for respawning (Sets your current docked base as your home base — you will respawn there if destroyed. No payload parameters; the base you are docked at is always used.). 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.
set_home_base accepts 2 parameters: base_id, session_id. Required: base_id, 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 set_home_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.
set_home_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 set_home_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 set_home_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.
set_home_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