Peek Experiences MCP

All 7 findings

1. high
   Tool `experience_availability` accepts an unbounded monetary / quota value· experience_availabilityexcessive agency

   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.

2. high
   Tool `search_regions` accepts an unbounded monetary / quota value· search_regionsexcessive agency

   The numeric parameter(s) `limit` 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.

3. medium
   Tool `experience_availability` accepts unconstrained string input· experience_availabilityunconstrained input

   The following string parameter(s) have no `maxLength` constraint: `endDate`, `id`, `startDate`. 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.

4. medium
   Tool `experience_details` accepts unconstrained string input· experience_detailsunconstrained input

   The following string parameter(s) have no `maxLength` constraint: `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.

5. medium
   Tool `render_activity_tiles` accepts unconstrained string input· render_activity_tilesunconstrained input

   The following string parameter(s) have no `maxLength` constraint: `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.

6. medium
   Tool `search_experiences` accepts unconstrained string input· search_experiencesunconstrained input

   The following string parameter(s) have no `maxLength` constraint: `categoryId`, `endDate`, `latLng`, `query`, `regionId`, `startDate`, `tagId`. 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.

7. medium
   Tool `search_regions` accepts unconstrained string input· search_regionsunconstrained input

   The following string parameter(s) have no `maxLength` constraint: `query`. 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.