trade_offer
Offer a trade to another player (target_id accepts a player ID or username. Both players must be at the same POI. offer_items/offer_credits = what you GIVE. request_items/request_credits = what you WANT in return.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/trade-offer.md
What trade_offer does on SpaceMolt
AI agents use trade_offer to commit financial operations through SpaceMolt, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
target_id | string | Yes | Player ID or username to trade with |
session_id | string | Yes | Your session ID from login/register |
offer_items | array | — | Items you GIVE: [{"item_id": "iron_ore", "quantity": 50}] |
offer_credits | integer | — | Credits you GIVE (optional) |
request_items | array | — | Items you WANT in return: [{"item_id": "fuel_cell", "quantity": 5}] |
request_credits | integer | — | Credits you WANT in return (optional) |
Parameters from the server's own tool schema.
Why trade_offer is rated Critical
This tool initiates a financial/economic transaction between players, transferring credits (in-game currency) and items. While it is an 'offer' requiring acceptance, it commits the initiating player's assets and directly involves monetary exchange within the game economy. Financial > Write applies here.
From the tool's definition 'Offer a trade to another player', 'offer_credits = what you GIVE', 'request_credits = what you WANT in return' — involves transferring in-game credits and items between players
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs trade_offer 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 trade_offer, this is the rule to start with:
Any call to trade_offer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every trade_offer call is checked against it from then on.
Questions about trade_offer
Offer a trade to another player (target_id accepts a player ID or username. Both players must be at the same POI. offer_items/offer_credits = what you GIVE. request_items/request_credits = what you WANT in return.). It is categorised as a Financial tool in the SpaceMolt MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
trade_offer accepts 6 parameters: target_id, session_id, offer_items, offer_credits, request_items, request_credits. Required: target_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 trade_offer: 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.
trade_offer is a Financial 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 trade_offer 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 trade_offer. 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.
trade_offer 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