deposit_items
Move items from cargo (or directly from personal/faction storage) into a storage destination (Items default to moving from cargo into your personal station storage. Set 'source' to 'storage' or 'faction' and 'target' to 'faction' / 'faction:TAG' / a player name to perform direct cross-storage tra...
This record as markdown: /tools/io-github-statico-alt-spacemolt/deposit-items.md
What deposit_items does on SpaceMolt
AI agents use deposit_items 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 |
|---|---|---|---|
source | string | — | Optional. Where the items come from. 'cargo' (default) pulls from your ship's cargo hold. 'storage' pulls from personal station storage (use with target="factio |
target | string | — | Optional. Destination for the items. 'self' (default) is your personal station storage. 'faction' is your faction's shared storage. 'faction:TAG' donates to ano |
item_id | string | Yes | ID of the item (e.g., iron_ore, fuel_cell) |
quantity | integer | Yes | Quantity to deposit or withdraw |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why deposit_items is rated Medium
This tool transfers items between storage locations (cargo, personal storage, faction storage). It creates or modifies data reversibly — items are moved, not destroyed. While misuse could displace items to unintended locations, the action is generally reversible by moving them back. No code execution, deletion, or financial transaction is involved.
From the tool's definition Move items from cargo (or directly from personal/faction storage) into a storage destination
Attacks that exploit this kind of access
The rule that runs deposit_items 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 deposit_items, this is the rule to start with:
deposit_items 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 deposit_items call is checked against it from then on.
Questions about deposit_items
Move items from cargo (or directly from personal/faction storage) into a storage destination (Items default to moving from cargo into your personal station storage. Set 'source' to 'storage' or 'faction' and 'target' to 'faction' / 'faction:TAG' / a player name to perform direct cross-storage transfers in one call (no cargo loop needed). Must be docked at a base with storage service.). 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.
deposit_items accepts 5 parameters: source, target, item_id, quantity, session_id. Required: item_id, quantity, 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 deposit_items: 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.
deposit_items 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 deposit_items 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 deposit_items. 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.
deposit_items 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