unload_passenger

2 findings on this tool

1. mediumunconstrained inputf-r1-unload_passenger

   Tool `unload_passenger` accepts unconstrained string input

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

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

   Description: "Put a single passenger off the ship at the current station (You must be docked. If this station is the passenger's destination they are delivered and pay their fare; otherwise they are stranded here, pay nothing, and you take a small reputation hit with their empire. Use 'list_passengers' to see who is aboard.)" -- 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 T0040