faction_submit_trade_intel
Submit market price observations to your faction's trade ledger (Manually report market prices you observed at other stations. Trust-based — your faction sees who reported what and when. Max 20 stations per submission. Requires a faction_trade_intel facility.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-submit-trade-intel.md
What faction_submit_trade_intel does on SpaceMolt
AI agents use faction_submit_trade_intel 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 |
|---|---|---|---|
stations | array | Yes | Array of station market reports (max 20 stations per submission) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why faction_submit_trade_intel is rated Medium
This tool creates or adds data (market price reports) to a persistent faction ledger. While it modifies shared game state, the impact is localized to informational records that other players can observe. There is no irreversible destruction, no execution of arbitrary code, no financial transactions, and no direct destructive capability.
From the tool's definition Tool submits/reports market price observations to a faction ledger. Description says 'Submit market price observations' and 'Manually report market prices' — these are write operations that create records in a shared ledger.
Attacks that exploit this kind of access
The rule that runs faction_submit_trade_intel 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_submit_trade_intel, this is the rule to start with:
faction_submit_trade_intel 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_submit_trade_intel call is checked against it from then on.
Questions about faction_submit_trade_intel
Submit market price observations to your faction's trade ledger (Manually report market prices you observed at other stations. Trust-based — your faction sees who reported what and when. Max 20 stations per submission. Requires a faction_trade_intel facility.). 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_submit_trade_intel accepts 2 parameters: stations, session_id. Required: stations, 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_submit_trade_intel: 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_submit_trade_intel 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_submit_trade_intel 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_submit_trade_intel. 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_submit_trade_intel 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