docs: add Enterprise prompt-injection screening page

[claude]

Requested by Micah Stairs · Slack thread

Before

Nothing on docs.firecrawl.dev describes screening scraped content for prompt-injection payloads. Readers who ask about it get pointed at Lockdown Mode, which does something else entirely. That conflation already exists inside the company.

After

A new Enterprise page, features/prompt-injection-screening, that says three things:

1. The problem. A scraped page is untrusted input. Text on the page can carry instructions aimed at whatever model reads it downstream. Hidden text is the concrete case — white-on-white, zero font size, off-screen positioning, and comparable tricks. A human viewing the page never sees them; a markdown or text conversion preserves them.
2. What it is not. It is not Lockdown Mode. Lockdown serves from Firecrawl's index and cache without an outbound request to the target — an egress and compliance control. It does not inspect content, and under Lockdown an unset maximum-age default is much longer, so a served page can be older. The page links to the Lockdown page and states the difference directly.
3. The behavior, conceptually. Content is classified, suspected injection is flagged, and the safe default is to withhold rather than pass it through silently. Policy is configurable per account.

How

• Added features/prompt-injection-screening.mdx, matching the frontmatter, heading style, Note-callout enterprise-gate convention, and voice of the existing features/threat-protection.mdx and features/siem.mdx pages.
• Registered the page in docs.json in the Enterprise nav group, next to Threat Protection and SIEM. Both English Enterprise groups (the visible one and the hidden duplicate) were updated. No localized nav entries and no localized files were touched, per CLAUDE.md.

Please read before merging

• This documents an Enterprise feature that is NOT yet wired into API parameters. The requester was explicit about this.
• No API surface is described. The page contains no request parameter, no field name, no response shape, and no code sample. There is nothing on it a reader could paste into an API call. That is deliberate, not an omission to fill in during review.
• No date or roadmap commitment appears anywhere on the page.
• The underlying screener exists today only as an internal component — an accepted ADR covering Firecrawl's own agents. So this page describes intent, not a shipped API.
• Do not merge until someone confirms the availability wording is what we want to say publicly. The page currently says the feature is an enterprise feature available through your account team. That sentence is the one to check.

Also worth a second opinion: whether this belongs on enterprise.mdx's feature list too. I left it off, since Threat Protection and SIEM are not listed there either.

Validation

• docs.json parses as valid JSON.
• Every page referenced anywhere in the navigation resolves to a real .mdx file (0 missing).
• The one internal link on the new page, /features/lockdown, resolves.
• Prettier was not run as a write step. The repo baseline is not Prettier-clean — docs.json, features/lockdown.mdx, and features/threat-protection.mdx all fail prettier --check on unmodified main — so reformatting would have buried this change in unrelated churn. The nav addition follows the file's existing 2-space indentation exactly; the diff is two added lines.
• No API code, types, or request parameters were changed. This repo is docs-only, and the diff is one new page plus two nav lines.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MGRyumQaNvjFxq8qFjm3o1

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
firecrawl	🟢 Ready	View Preview	Aug 21, 2026, 6:58 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.