send_gift
Send items, credits, or a ship to another player or to an empire at this station (recipient accepts a player username/ID, an empire alias ('solarian', 'voidborn', 'crimson', 'nebula', 'outerrim' — also accepts long names like 'Solarian Confederacy' or 'empire:crimson'), or 'faction:TAG' for anoth...
This record as markdown: /tools/io-github-statico-alt-spacemolt/send-gift.md
What send_gift does on SpaceMolt
AI agents use send_gift 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 | — | Where item gifts come from: 'cargo' (default) pulls from your ship's cargo hold; 'storage' pulls directly from your personal station storage, skipping the withd |
credits | integer | — | Credits to transfer from your wallet. Mutually exclusive with ship_id. |
item_id | string | — | ID of the item to send from your cargo (e.g., iron_ore, fuel_cell). Mutually exclusive with ship_id. |
message | string | — | Optional message to include with the gift (max 500 characters). |
ship_id | string | — | Unique instance ID of a ship to transfer to the recipient (use list_ships to find ship IDs). Remote: the ship can be parked at any station and you need not be d |
quantity | integer | — | Number of items to send. Required if item_id is specified. |
recipient | string | Yes | Username of the player to gift (case-insensitive). They do NOT need to be online or at this station — delivery is async. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why send_gift is rated Medium
send_gift performs reversible asset transfers (items, credits, ships) between players and factions. This is a Write operation because it modifies game state and creates new data relationships, but is reversible (gifts can presumably be rejected, traded back, or redistributed).
From the tool's definition Tool description states 'Send items, credits, or a ship to another player or to an empire' — this modifies game state by transferring assets between players/entities. The tool creates new ownership relationships and removes assets from the caller's inventory.
Attacks that exploit this kind of access
The rule that runs send_gift 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 send_gift, this is the rule to start with:
send_gift 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 send_gift call is checked against it from then on.
Questions about send_gift
Send items, credits, or a ship to another player or to an empire at this station (recipient accepts a player username/ID, an empire alias ('solarian', 'voidborn', 'crimson', 'nebula', 'outerrim' — also accepts long names like 'Solarian Confederacy' or 'empire:crimson'), or 'faction:TAG' for another faction. Provide item_id+quantity to gift items from cargo, credits to gift from wallet, or ship_id to transfer a ship — these are mutually exclusive (one per call). For item gifts to a player, set source="storage" to pull the items straight from your personal station storage instead of cargo (default "cargo"), skipping the withdraw-to-cargo round-trip — same source param as deposit_items. Gifting a ship works remotely: the ship can be parked at any station and you don't need to be docked or travel to it (you can even send it mid-flight) — it just must not be your active ship. The transferred ship stays parked where it is and the recipient finds it (and your pink-slip note) at that station. Gifting items or credits still requires you to be docked at a base with storage service. Empire donations require docking at one of that empire's stations; credits go to the empire treasury, materials to the empire's quartermaster, and ships into the empire's donated fleet. Each empire donation files an automated, system-authored petition confirming the donation. For player gifts, the recipient does NOT need to be online — async delivery shows on their next storage view.). 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.
send_gift accepts 8 parameters: source, credits, item_id, message, ship_id, quantity, recipient, session_id. Required: recipient, 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 send_gift: 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.
send_gift 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 send_gift 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 send_gift. 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.
send_gift 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