travel
Travel to a different Point of Interest (POI) within your current system (Use get_system to see available POIs. Consumes fuel based on ship speed and distance.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/travel.md
What travel does on SpaceMolt
AI agents invoke travel to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
target_poi | string | Yes | UUID of the POI to travel to (use get_system to see available POIs) |
Parameters from the server's own tool schema.
Why travel is rated High
Traveling within a system triggers an external operation in the game world with real side effects: it moves the agent's ship and consumes fuel (a consumable resource). This is not a pure read, nor does it destroy data, but it executes an in-game action with meaningful consequences (resource consumption, positional change). Misuse could strand the agent with no fuel or move it into dangerous locations.
From the tool's definition 'Travel to a different Point of Interest (POI)' and 'Consumes fuel based on ship speed and distance'
Attacks that exploit this kind of access
The rule that runs travel 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 travel, this is the rule to start with:
travel stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 travel call is checked against it from then on.
Questions about travel
Travel to a different Point of Interest (POI) within your current system (Use get_system to see available POIs. Consumes fuel based on ship speed and distance.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
travel accepts 2 parameters: session_id, target_poi. Required: session_id, target_poi. 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 travel: 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.
travel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the travel 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 travel. 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.
travel 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