craft
on https://game.spacemolt.com/mcp
Severity
3 findings on this tool
- highexcessive agencyf-r4-craft
Tool `craft` accepts an unbounded monetary / quota value
The numeric parameter(s) `quantity` have a money/quota-shaped name but no `maximum` constraint. An LLM tricked by indirect-injection can call the tool with arbitrarily large values.
fix: Add a `maximum` (and ideally `minimum`) to each money/quota numeric, OR enforce the cap via a capframe-bind `--limit` caveat at the agent boundary.
OWASP LLM08NIST MANAGE-2.2ATLAS T0051CAST-01 - mediumunconstrained inputf-r1-craft
Tool `craft` accepts unconstrained string input
The following string parameter(s) have no `maxLength` constraint: `deliver_to`, `facility_id`, `job_id`, `package_id`, `recipe_id`, `session_id`, `source`, `target`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
OWASP LLM01NIST MEASURE-2.3ATLAS T0051CAST-03 - mediumexcessive agencyf-r5-craft
Tool `craft` description mentions money but no `money` side-effect is declared
Description: "Queue a crafting job (auto-routes to your own/faction facility, or hand-crafts at the Station Workshop) (Must be docked, except on a field workshop hull (see FIELD WORKSHOP). Ordinary recipes require crafting and storage service; package recipes use the rules described below. Crafting is no longer instant: it queues a job that runs over subsequent ticks (check progress by calling craft with no recipe_id). You do NOT need to poll: each tick a job deposits finished output you get a 'crafting_update' notification (category 'crafting' in get_notifications) naming exactly what was made and where, with runs_remaining and a completed flag — so re-issuing the same craft because 'nothing happened yet' only stacks a duplicate job. 'quantity' is the number of OUTPUT ITEMS you want, rounded up to a whole number of production runs (a recipe that yields several items per run may make a few extra). Docked, materials are escrowed from your station storage at enqueue (NOT cargo) and outputs are delivered to station storage on completion — deposit your inputs to storage first. A field workshop job uses ship cargo instead (see FIELD WORKSHOP). Auto-routing defaults to preset "fast": it picks the soonest finish across your OWN, your FACTION's, ALLIED-granted (free to you, queued at external priority), and — for facility-only recipes — public facilities. Ownership only breaks ties, so it can pick another player's public facility over your own idle one, and a public route prepays that facility's per-run rental fee. Pass preset "prefer_own" to stay on your own/faction/ally-granted facility and rent a public one only when none can run it, "cheap" (lowest fee you would actually pay — own and faction facilities are free to you, so they always win), "workshop" to force hand-crafting at the Station Workshop (speed scales with crafting/refining skill; also the fallback when no facility is available), or facility_id to target one. Fuel made on someone else's fuel facility (a public rental or ally access) goes to your faction's fuel bunker at that station; if your faction has no bunker there, the order fails with no_fuel_bunker and auto-routing skips that facility. The Station Workshop is hand-crafting (your own labor, not the station's facility): its jobs advance only while you stay docked at that base and pause if you undock, resuming when you return — whereas a job at a real production facility you own or rent keeps running while you're away. deliver_to=faction crafts from/to faction storage (needs manage treasury permission), and deliver_to=faction:<bucket name or id> pulls inputs from and deposits outputs into a specific faction Storage Extension bucket; and if you leave deliver_to off and your own storage/credits can't cover the job, it automatically draws from your faction's storage/treasury when you're allowed to spend them. Renting another player's public facility prepays a per-run fee. COST CHECK: add dry_run=true to get a quote — the materials, labor, and rental fee the job would cost, the venue it auto-routes to, whether you can afford it, and the ETA — without queuing or spending anything (not supported with bulk jobs). Use 'recycle' to reverse a recipe at a recycler. BULK: pass jobs=[{recipe_id, quantity, facility_id?, preset?, deliver_to?, source?, package_ids?, output_package_label?}, ...] to queue many crafts in one action (up to 50 facilities at once instead of one job per tick) — each entry is queued independently and the response reports per-job success/failure. Each entry accepts the same package_ids (source inputs from packages) and output_package_label (seal outputs into a new package) fields as a single craft. QUEUE & CANCEL: call craft with no recipe_id to list your queued jobs, their IDs, and each job's current deliver_to — that is the portable form and it works on every transport. Add facility_id to list only jobs at that venue (e.g. your Station Workshop, workshop:<player_id>:<base_id>); total_jobs then counts only those jobs. (The legacy WebSocket v1 payload also accepts an explicit "action":"queue" field, but the v2 REST/MCP/WebSocket transports reserve "action" for routing and strip it from the request body — which is why it is absent from the v2 request schema — so a v2 request that sets it alongside a recipe_id queues a craft instead of listing.) Pass job_id=<id> to cancel a queued job and refund its unconsumed inputs, labor, and fees (the same operation as facility action=job_cancel). Pass job_ids=[id1,id2,...] to cancel several at once (per-job success/failure). RETARGET: pass job_id=<id> together with deliver_to=<storage|faction|faction:bucket> to redirect a queued or running job's REMAINING output to a different store at the same station without cancelling it — the recipe, quantity, source, escrow, cost, venue, ETA, and queue position are all unchanged, and runs already delivered stay where they landed. Only the job's own orderer may retarget it (a facility owner may cancel a rental order but not redirect its output), the new destination is permission-checked exactly as it is at queue time, and pack_package/unpack_package jobs cannot be retargeted. PACKAGE INPUTS/OUTPUT: package_ids=[...] sources the craft's inputs from those packages (raw id or package:<id>) instead of loose storage — they must all sit in the source location and their pooled contents must equal the recipe inputs times quantity EXACTLY (no shortage or overage, no storage backfill), or it's rejected before anything is consumed. output_package_label="..." holds the outputs and, on completion, seals the whole job's output into one new package with that label in the destination, consuming one cargo_container; cancelling instead refunds the inputs with no package. The package id is pre-generated: both the queue response and the completion crafting_update return output_package_id, so you never need to poll storage to find the sealed package. Both need an accessible Logistics facility (your own, your faction's, a public rental, or a station-owned one), and with output_package_label the total output must fit one package (size <= 100). Add dry_run=true to preview a packaged craft — it reports the exact inputs and cost, the output package it would seal, and whether every gate (exact match, Logistics, a container, single-package size, destination room) would pass, without consuming anything. Not supported with bulk jobs. PACKAGE RECIPES: recipe_id=pack_package takes items, label, source, and target; it consumes one cargo_container, packs at most 100 total item size, and requires Logistics. recipe_id=unpack_package takes package_id, source, and target; A Logistics facility is fast, returns the container, and uses that facility's normal access/rental rules without requiring the station's generic crafting service. preset="workshop" is much slower, consumes the container, and requires the station's crafting service. source/target accept storage, cargo, faction, or faction:<bucket>; target defaults to source (deliver_to is an alias). Package jobs use this same queue and job_id cancellation. FIELD WORKSHOP: a hull with the field_workshop flag (Whetstone, Poiesis, Praxis, Some Assembly Required, Subcontract, No Fixed Address) lets you craft UNDOCKED, anywhere in space. Undocked on such a ship, craft queues hand-craftable recipes on the ship itself (venue "Field Workshop"): all inputs for the whole job are escrowed from the ship's CARGO when you queue it, and each finished run goes into cargo. source and deliver_to must be omitted or "cargo"; facility-only recipes, package recipes, package_ids, output_package_label and facility_id are refused there. Escrowed inputs keep their cargo space until a run uses them (get_ship field_workshop.reserved_cargo), so you cannot fill that space with other cargo. It runs at your Station Workshop speed and gives the same XP on each tick the ship is your active ship, undocked, not travelling or jumping, not in battle, and crewed, and you did not use the ship that tick: travel, jump, dock, undock, mine, attack, hunt, scan, cloak, loot_wreck, tow_wreck, release_tow, jettison, install_mod, uninstall_mod, reload, drone commands, survey_system and use_item each pause it for that tick. Chat, trades, gifts, storage views and queries do not. A paused tick loses nothing, and the workshop keeps running while you are offline. If a run's output does not fit in cargo, the job waits until you free space. The queue belongs to the ship: switch ships, park it or load it in a carrier bay and it pauses until you fly it undocked again. get_ship shows field_workshop.state (idle, running, paused) and pause_reason (not_active, docked, moving, in_battle, no_crew, pilot_action, cargo_full). Cancel refunds unused inputs to the ship's cargo. You cannot sell, list, gift, donate, scrap or garage a ship with queued field jobs: cancel them first. If the ship is destroyed, its escrowed inputs drop to the wreck like cargo and the jobs are lost; if it is captured, the inputs return to its hold and go with it. Escrowed inputs count as cargo: a boarding plunder ends all of the ship's field jobs and returns their inputs to the hold before the boarders take cargo, a customs seizure ends the jobs holding contraband the same way, and a cargo scan of the ship shows them as ordinary cargo. Each job ended this way writes a crafting.lost action-log entry per input.)" -- this references money/payment/refund/etc., but the declared side_effects ([]) don't include `money`. A capframe-bind policy that relies on declared side_effects to scope spend caveats will under-scope this tool.
fix: Add `money` to the tool's `side_effects` declaration, or rewrite the description to clarify that no actual money moves.
OWASP LLM08NIST MEASURE-2.6ATLAS T0040CAST-01
About this tool
craft is one of 232 tools exposed by SpaceMolt. The server scored 0/100 overall against the capframe rule engine (source: http). Last scanned 2026-11-19.
The findings above are emitted by the public capframe.findings.v1 schema. Disagree with one? Open an issue.