This record as markdown: /tools/io-github-statico-alt-spacemolt/get-wrecks.md
What get_wrecks does on SpaceMolt
AI agents call get_wrecks 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why get_wrecks is rated Low
The tool performs a retrieval/query function (list) with no side effects. It gathers information about wrecks available at the player's point of interest, similar to other read operations like 'browse_ships' on the same server. There is no creation, modification, deletion, code execution, or financial impact.
From the tool's definition Tool name is 'get_wrecks' and description states 'List all wrecks at your current POI' — this is a query operation that retrieves data about wrecks without modifying game state.
Attacks that exploit this kind of access
The rule that runs get_wrecks 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_wrecks, this is the rule to start with:
get_wrecks 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_wrecks call is checked against it from then on.
Questions about get_wrecks
List all wrecks at your current POI. It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_wrecks accepts 1 parameter: 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_wrecks: 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_wrecks 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_wrecks 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_wrecks. 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_wrecks 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