accept_mission
on https://game.spacemolt.com/mcp
Severity
2 findings on this tool
- mediumunconstrained inputf-r1-accept_mission
Tool `accept_mission` accepts unconstrained string input
The following string parameter(s) have no `maxLength` constraint: `mission_id`, `session_id`, `template_id`. 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-accept_mission
Tool `accept_mission` description mentions money but no `money` side-effect is declared
Description: "Accept a mission from the mission board (You must be docked at the base offering the mission. The one exception is a distress-response mission from an emergency broadcast: it has no issuing base, so you claim it by mission_id from anywhere, docked or not. Maximum 5 active missions at once. Use get_missions to see available missions and their IDs. Courier cargo requires enough available fixer allowance. Only one restitution job can be active at once. Faction postings pay only the first pilot to complete them. If a prerequisite mission is missing, the mission_not_available error names each one and the next step toward it. A local archive mission instead requires presence at its charted offer POI; get_poi shows that private offer. no_expiry=true means there is no deadline and expires_at is empty.)" -- 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
accept_mission 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.