firecrawl-policy

Enforces transport, consent, URL, and evidence gates for Firecrawl CLI operations.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-policy-leonardoacosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-policy
Source: https://github.com/leonardoacosta/agents/tree/main/skills/firecrawl-policy
Command: npx skills add https://github.com/leonardoacosta/agents --skill firecrawl-policy-leonardoacosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Firecrawl operations can leak credentials, fetch unsafe URLs, mutate account state, or exfiltrate private files when agents act without guardrails. This Skill supplies a mandatory supplemental policy that constrains every firecrawl-* core, build, or workflow skill with strict local safety gates. ## Core Features & Use Cases - Fail-closed URL gate: Validates every URL through literal argv, HTTPS-only checks, DNS resolution, and redirect trust boundaries before any fetch. - Consent and egress controls: Requires action-level consent for browser interactions and explicit approval before parsing sensitive local files through Firecrawl. - Secret and evidence handling: Blocks API keys in argv, enforces 0700/0600 evidence permissions, and mandates scrubbing of cookies, tokens, and PII. - Use Case: When an agent is asked to scrape a customer URL or parse a confidential PDF, this policy forces URL validation, egress disclosure, and approval checks before any command runs. ## Quick Start Load the firecrawl-policy skill alongside any firecrawl skill so its safety gates apply to every Firecrawl operation.

Frequently Asked Questions about firecrawl-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely scrape a URL with the Firecrawl CLI?

Validate the URL through the fail-closed gate before running firecrawl scrape: use literal argv without a shell, accept only absolute HTTPS URLs, reject userinfo and private IP ranges, and resolve all A and AAAA records immediately before submission.

When can I use the Firecrawl SDK instead of the CLI?

An official Firecrawl SDK is permitted only in shipped application code after supply-chain review with an exact pinned version and lockfile. Agent-side research, validation, and smoke tests must always use the installed CLI, never an SDK, MCP, or direct REST.

Can Firecrawl parse local files containing sensitive data?

Firecrawl parse sends local file contents to Firecrawl's servers, so this egress must be disclosed first. Confidential, personal, or regulated content requires explicit approval naming the file and data class before upload; otherwise the operation is refused.

What happens if the Firecrawl CLI does not support an operation?

The agent stops and reports a capability gap with the CLI version, help inspected, and the unsupported capability. A fallback to one named MCP server or REST endpoint is allowed only after explicit user approval; an invocation error alone never authorizes switching transport.

Does the public research allowance permit scraping private or authenticated URLs?

No. The public hosted research allowance covers only unauthenticated public search and scrape after URL and DNS validation. Authenticated browsing, customer data, or local-network fetching requires per-hop redirect validation or enforced destination constraints, otherwise it fails closed.