Check the status of a crawl job
AI agents call firecrawl_crawl_status to retrieve information from Firecrawl Local MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it queries the status of an existing crawl job and returns status information. There are no side effects, no code execution, no data modification, and no irreversible actions. It is purely informational retrieval, fitting the 'Read' category with low severity due to its passive nature and limited blast radius if misused.
From the tool's definition Tool name 'firecrawl_crawl_status' and description 'Check the status of a crawl job' indicate a query operation that retrieves job status information without modifying or executing anything.
Attacks that exploit this kind of access
Check the status of a crawl job. It is categorised as a Read tool in the Firecrawl Local MCP MCP Server, which means it retrieves data without modifying state.
Register the Firecrawl Local MCP server in PolicyLayer and add a rule for firecrawl_crawl_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Firecrawl Local MCP. Nothing to install.
firecrawl_crawl_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the firecrawl_crawl_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for firecrawl_crawl_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
firecrawl_crawl_status is provided by the Firecrawl Local MCP server (viperblackskull/firecrawl-local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →