The allowed npx CLI is not pinned to a package version
Source references: 3Tool permissions allow any `npx firecrawl-cli` subcommand, but the Skill pins neither a package version nor an integrity digest. If it is not locally cached, npx may resolve and run a current registry release; the supplied text specifies no provenance verification.
If resolution selects a compromised, impersonating, or destructively changed package version, its code may run with the agent process’s privileges and access files, environment variables, and networks available to that process.
The allowed-tools pattern does include `npx firecrawl-cli` without a stated version, but the body never invokes that command and provides no visible installation or package-resolution behavior. A permission declaration alone cannot establish whether a remote package will be downloaded and executed, or whether the environment pins, caches, or wraps it. Users can ask the author to document the source and pin the version and integrity.
This assessment concerns the code and conditions shown, not proof that harm has occurred. Drive a live browser on a scraped page: click, fill forms, log in, paginate, infinite-scroll. Use when content requires interaction or a scrape failed or returned incomplete content.allowed-tools: - Bash(firecrawl *) - Bash(npx firecrawl-cli *)---Show 2 other places
```bash# 1. Scrape a page (scrape ID is saved automatically)firecrawl scrape "<url>"Run `firecrawl interact --help` for the full option list.