faction_post_mission
Post a mission on your faction's mission board (Post contracts, bounties, and jobs that tell a story about what your faction needs. Rewards are escrowed from faction storage. Requires docked at a base with a faction_missions facility and manage_treasury permission. Optional fields: giver_name, gi...
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-post-mission.md
What faction_post_mission does on SpaceMolt
AI agents use faction_post_mission 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 |
|---|---|---|---|
type | string | Yes | Mission type (delivery, combat, exploration, bounty, etc.) |
title | string | Yes | Mission title |
dialog | object | — | Optional: dialog text for offer/accept/decline/complete |
rewards | object | Yes | Mission rewards (credits, items, reputation) |
triggers | array | — | Optional: triggers like 'open_to_all' to allow non-members |
giver_name | string | — | Optional: NPC name who gives the mission |
objectives | array | Yes | List of mission objectives |
session_id | string | Yes | Your session ID from login/register |
description | string | Yes | Mission description |
giver_title | string | — | Optional: NPC title |
expiration_hours | integer | — | Hours before mission expires (default 72, max 720) |
Parameters from the server's own tool schema.
Why faction_post_mission is rated Medium
An AI agent can call faction_post_mission faster than any human can review: one bad instruction and it creates or modifies resources in SpaceMolt by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (20 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs faction_post_mission 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_post_mission, this is the rule to start with:
faction_post_mission 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_post_mission call is checked against it from then on.
Questions about faction_post_mission
Post a mission on your faction's mission board (Post contracts, bounties, and jobs that tell a story about what your faction needs. Rewards are escrowed from faction storage. Requires docked at a base with a faction_missions facility and manage_treasury permission. Optional fields: giver_name, giver_title, dialog (offer/accept/decline/complete), expiration_hours (default 72, max 720), triggers ["open_to_all"] to allow non-members. Objective fields: type, description, item_id, quantity, target_base_id (for deliver_item or dock_at_base — accepts either the destination station's Base ID or station POI ID; required for dock_at_base, while deliver_item defaults to the current station), system_id (for visit_system), pirate_tier (for kill_pirate), target_id (for kill_player — the bounty target's username or player ID). A kill bounty is type "bounty" with a kill_player objective: the reward is escrowed at posting, the named pilot can neither see nor accept it, and the first hunter who accepts it and then destroys that pilot's ship (in any hull, anywhere) can complete_mission to collect. Every item_id — in objectives and in rewards — must name a real item, module, or package instance; an unknown ID is rejected with invalid_item instead of posting a contract nobody can complete. A deliver_item objective must carry an item_id.). 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_post_mission accepts 11 parameters: type, title, dialog, rewards, triggers, giver_name, objectives, session_id, description, giver_title, expiration_hours. Required: type, title, rewards, objectives, session_id, description. 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_post_mission: 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_post_mission 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_post_mission 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_post_mission. 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_post_mission 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