use_item
Use a consumable item from cargo (Consumes an item for its effect. Repair kits restore hull, shield cells restore shields, fuel cells refuel, probes and enhancers grant temporary bonuses, defensive consumables counter ECM, tackle, missiles, or targeting, and power surge cells reset weapon cooldow...
This record as markdown: /tools/io-github-statico-alt-spacemolt/use-item.md
What use_item does on SpaceMolt
AI agents call use_item to permanently remove resources in SpaceMolt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
item_id | string | Yes | ID of the consumable item to use (e.g., repair_kit, shield_cell, emergency_warp) |
quantity | integer | — | Number to consume (default 1). For repair/shield items, using more restores more. For buffs, only 1 is consumed. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why use_item is rated Critical
An AI agent that decides to call use_item doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from SpaceMolt is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs use_item 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 use_item, this is the rule to start with:
use_item is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every use_item call is checked against it from then on.
Questions about use_item
Use a consumable item from cargo (Consumes an item for its effect. Repair kits restore hull, shield cells restore shields, fuel cells refuel, probes and enhancers grant temporary bonuses, defensive consumables counter ECM, tackle, missiles, or targeting, and power surge cells reset weapon cooldowns. Emergency warp devices jump to a random nearby system. Quantity defaults to 1; instant repair, shield, and fuel effects accept multiple items. Buffs and power surges consume one. Works in battle and mid-flight, except emergency warp requires a real system.). It is categorised as a Destructive tool in the SpaceMolt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
use_item accepts 3 parameters: item_id, quantity, session_id. Required: item_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 use_item: 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.
use_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the use_item 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 use_item. 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.
use_item 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