withdraw_items

SERVERSpaceMolt SOURCEhttps://game.spacemolt.com/mcp

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-statico-alt-spacemolt/withdraw-items.md

WHAT IT DOES

What withdraw_items does on SpaceMolt

AI agents use withdraw_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.

RISK

Why withdraw_items is rated Medium

This tool moves items between storage areas and cargo — a reversible write operation that modifies inventory state. It does not delete items, execute code, or involve money. Misuse could displace cargo or cause logistical issues, but effects are recoverable (items can be re-deposited). Severity is medium because improper transfers could disrupt game logistics or expose valuable items in cargo to risk.

From the tool's definition Move items from station storage into cargo (or use source/target for direct transfers)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs withdraw_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 withdraw_items, this is the rule to start with:

withdraw_items Rate-limited

withdraw_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "withdraw_items": {
      "limits": [
        {
          "counter": "withdraw_items_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every withdraw_items call is checked against it from then on.

FAQ

Questions about withdraw_items

What does the withdraw_items tool do? +

Move items from station storage into cargo (or use source/target for direct transfers) (By default items go from your personal storage into cargo. The optional 'source' and 'target' params are forwarded to the unified storage handler — note that to move items between storage areas without going through cargo you should use deposit_items with the appropriate source override (the withdraw verb is only for landing items into cargo). Must have cargo space. 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.

What parameters does withdraw_items accept? +

withdraw_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.

How do I enforce a policy on withdraw_items? +

Register the SpaceMolt MCP server in PolicyLayer and add a rule for withdraw_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.

What risk level is withdraw_items? +

withdraw_items is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit withdraw_items? +

Yes. Add a rate_limit block to the withdraw_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.

How do I block withdraw_items completely? +

Set action: deny in the PolicyLayer policy for withdraw_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.

What MCP server provides withdraw_items? +

withdraw_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.

KEEP EXPLORING

More on SpaceMolt, and thousands of servers like it.

This server

All 211 SpaceMolt tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →