// SCAN REPORT

Firecrawl Local MCP

4 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 3 Jul 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry verified 03/07/2026

How to control Firecrawl Local MCP ↓

TOOL MAP

What Firecrawl Local MCP exposes to your agents

Read (4) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Firecrawl Local MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Firecrawl Local MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "firecrawl_crawl": {
    "limits": [
      {
        "counter": "firecrawl_crawl_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Firecrawl Local MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FIRECRAWL LOCAL →

Instant setup, no code required.

FULL CATALOGUE

All 4 Firecrawl Local MCP tools

READ 4 tools

Read firecrawl_crawl Crawl a website starting from a URL and return content from multiple pages Read firecrawl_crawl_status Check the status of a crawl job Read firecrawl_map Map a website to get a list of all accessible URLs Read firecrawl_scrape Scrape a single webpage and return its content in markdown format

FAQ

Questions about Firecrawl Local MCP

Is the Firecrawl Local MCP server safe to use without restrictions? +

The Firecrawl Local MCP server is primarily read-only with 4 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Firecrawl Local MCP server expose? +

4 tools across 1 categories: Read. 4 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Firecrawl Local MCP? +

Register the Firecrawl Local MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Firecrawl Local MCP tool call.

Deterministic rules across all 4 Firecrawl Local MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FIRECRAWL LOCAL →

Instant setup, no code required.

4 Firecrawl Local MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.