get_base_cost

2 findings on this tool

1. mediumunconstrained inputf-r1-get_base_cost

   Tool `get_base_cost` accepts unconstrained string input

   The following string parameter(s) have no `maxLength` constraint: `session_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
2. mediumexcessive agencyf-r5-get_base_cost

   Tool `get_base_cost` description mentions money but no `money` side-effect is declared

   Description: "Preview the cost and requirements to found a faction station, plus the outpost founding fee (Returns the station core item, founding fee, `outpost_founding_fee` (the build_outpost fee, not refunded on dismantle), per-faction station cap, the full requirements, and whether your current location is an eligible founding spot.)" -- 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