firecrawl_monitor_delete

3 findings on this tool

1. highexcessive agencyf-r3-firecrawl_monitor_delete

   Tool `firecrawl_monitor_delete` name implies a side effect that is not declared

   `firecrawl_monitor_delete` looks like a side-effecting tool (its name contains a mutation verb), but its `side_effects` declaration is []. A policy synthesizer cannot produce safe rules for this tool because it cannot tell what it actually does.

   fix: Declare the tool's true side effects explicitly. If the tool is genuinely read-only, rename it to match (e.g. `email.preview` rather than `email.send`).

   OWASP LLM08NIST MEASURE-2.6ATLAS T0051
2. mediumunconstrained inputf-r1-firecrawl_monitor_delete

   Tool `firecrawl_monitor_delete` accepts unconstrained string 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.

   OWASP LLM01NIST MEASURE-2.3ATLAS T0051
3. mediumindirect injectionf-r6-firecrawl_monitor_delete

   Tool `firecrawl_monitor_delete` fetches external web content -- indirect-injection surface

   Description: " Permanently delete a monitor and stop its schedule. This cannot be undone. **Usage Example:** ```json { "name": "firecrawl_monitor_delete", "arguments": { "id": "mon_abc123" } } ``` " -- this tool pulls externally-controlled content into the agent's context window, the canonical indirect-injection vector. Even when the user supplies the URL, content at that URL can carry hostile instructions.

   fix: Sandbox the fetched content: strip prompts before forwarding to the model, constrain to an allow-list of domains, and route through capframe-guard with a `domain in [...]` caveat.

   OWASP LLM01NIST MEASURE-2.3ATLAS T0051