faction_withdraw_items
Move items from faction storage to your cargo (or use source/target for direct transfers) (Requires manage_treasury permission. Default destination is cargo (must have cargo space). The optional 'source' and 'target' params are forwarded to the unified storage handler — to move items from faction...
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-withdraw-items.md
What faction_withdraw_items does on SpaceMolt
AI agents use faction_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. Defaults to 'cargo'. Set to 'storage' on faction_deposit_items to move directly from personal storage into faction storage |
target | string | — | Optional. Destination for the items. Defaults to 'faction' (your faction's storage). Override only when you need a different routing — see the spacemolt_storage |
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 faction_withdraw_items is rated Medium
This tool moves items between storage locations (faction storage to cargo or other targets). It is a data/inventory transfer operation that is reversible (items can be re-deposited), so it fits Write rather than Destructive. However, it requires special permissions ('manage_treasury') and is audit-logged, indicating it has meaningful side effects and potential for misuse (e.g., draining faction resources).
From the tool's definition Move items from faction storage to your cargo (or use source/target for direct transfers)
Attacks that exploit this kind of access
The rule that runs faction_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 faction_withdraw_items, this is the rule to start with:
faction_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.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every faction_withdraw_items call is checked against it from then on.
Questions about faction_withdraw_items
Move items from faction storage to your cargo (or use source/target for direct transfers) (Requires manage_treasury permission. Default destination is cargo (must have cargo space). The optional 'source' and 'target' params are forwarded to the unified storage handler — to move items from faction storage directly into your personal storage in one call, prefer deposit_items with source="faction" and target="self". All withdrawals are tracked in the audit log.). 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.
faction_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.
Register the SpaceMolt MCP server in PolicyLayer and add a rule for faction_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.
faction_withdraw_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 faction_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.
Set action: deny in the PolicyLayer policy for faction_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.
faction_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.
More on SpaceMolt, and thousands of servers like it.
This server
Across the catalogue