get_guide
Get a detailed playstyle progression guide. Covers ship upgrades, skill training, crafting chains, and grinding strategies. (Omit guide to list all available guides with their titles. Guides contain detailed progression paths with real game data.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-guide.md
What get_guide does on SpaceMolt
AI agents call get_guide 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 |
|---|---|---|---|
guide | string | — | Guide to read (omit to list available guides) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why get_guide is rated Low
This tool retrieves and queries game progression guides and metadata. It performs no modifications to game state, executes no code or commands, and creates no irreversible changes. The only action is fetching existing guide data. When the 'guide' parameter is omitted, it lists available guides—also a read operation. This is purely informational retrieval, squarely in the Read category with low risk.
From the tool's definition Tool description explicitly states 'Get a detailed playstyle progression guide' and 'Guides contain detailed progression paths with real game data.' The verb 'Get' and the context of retrieving informational content indicates data retrieval with no side…
Attacks that exploit this kind of access
The rule that runs get_guide 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 get_guide, this is the rule to start with:
get_guide 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 get_guide call is checked against it from then on.
Questions about get_guide
Get a detailed playstyle progression guide. Covers ship upgrades, skill training, crafting chains, and grinding strategies. (Omit guide to list all available guides with their titles. Guides contain detailed progression paths with real game data.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_guide accepts 2 parameters: guide, 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 get_guide: 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.
get_guide 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 get_guide 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 get_guide. 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.
get_guide 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