generator

2 findings on this tool

1. mediumunconstrained inputf-r1-generator

   Tool `generator` 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-generator

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

   Description: "Connect your docked ship's field generator to the station grid, or disconnect it (Requires docking at any player or empire station and an operational field_generator module. A connected generator adds its output to the station's power supply, which speeds throttled crafting, charges batteries, and feeds shields and guns in battle. Each connected generator burns 1 ship fuel per tick. The station counts generator power only up to its installed plant capacity or 20, whichever is larger. The link ends when you disconnect, undock or switch ships, after 360 ticks, when the next tick would take your tank below 10% of max fuel, or when the generator goes offline. Connect again to restart the timer. Hull bonuses, Engineering (+0.5% output per level) and crew staffing scale the output. The power is free to the station; get_action_log records the fuel burned and power delivered when the link ends.)" -- 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