loot_wreck
Loot items and modules from a wreck (If wreck_id is omitted while towing a wreck, defaults to your towed wreck. Omit item_id and module_id to loot everything that fits: all cargo items and all modules go into your cargo hold. To loot a specific cargo item: include item_id and optional quantity. T...
This record as markdown: /tools/io-github-statico-alt-spacemolt/loot-wreck.md
What loot_wreck does on SpaceMolt
AI agents use loot_wreck 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 |
|---|---|---|---|
item_id | string | — | Specific cargo item ID to loot. Omit to loot everything (all cargo and modules go to cargo hold). |
quantity | integer | — | Quantity of cargo item to loot (only used with item_id) |
wreck_id | string | — | UUID of the wreck to loot. Omit when towing a wreck to default to your towed wreck. |
module_id | string | — | Module instance ID to loot directly onto your ship (requires free slot, CPU, and power). Get module IDs from get_wrecks. CPU and power usage shown reflect your |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why loot_wreck is rated Medium
Looting transfers items from a wreck into the agent's inventory/ship, which is a reversible write operation (items are moved/created in the agent's possession). It does not destroy or permanently delete data in an irreversible way — wrecks are already destroyed objects and looting is a standard game mechanic akin to picking up or acquiring items.
From the tool's definition Loot items and modules from a wreck... all cargo items and all modules go into your cargo hold... To loot a specific module directly onto your ship (fitting it)
Attacks that exploit this kind of access
The rule that runs loot_wreck 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 loot_wreck, this is the rule to start with:
loot_wreck 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 loot_wreck call is checked against it from then on.
Questions about loot_wreck
Loot items and modules from a wreck (If wreck_id is omitted while towing a wreck, defaults to your towed wreck. Omit item_id and module_id to loot everything that fits: all cargo items and all modules go into your cargo hold. To loot a specific cargo item: include item_id and optional quantity. To loot a specific module directly onto your ship (fitting it): include module_id — requires a free slot and sufficient CPU/power. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).). 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.
loot_wreck accepts 5 parameters: item_id, quantity, wreck_id, module_id, 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 loot_wreck: 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.
loot_wreck 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 loot_wreck 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 loot_wreck. 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.
loot_wreck 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