Check the status of a crawl job. Usage Example: json { "name": "firecrawl_check_crawl_status", "arguments": { "id": "550e8400-e29b-41d4-a716-446655440000" } } Returns: Status and progress of the crawl job, including results if available.
AI agents call firecrawl_check_crawl_status to retrieve information from Firecrawl Web Scraping Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Crawl job ID to check |
Parameters from the server's own tool schema.
This tool performs a pure query operation to retrieve the current state of an asynchronous crawl job. It has no side effects, does not modify data, and does not execute operations. This is a straightforward read/query action returning job metadata and progress information.
From the tool's definition The tool 'firecrawl_check_crawl_status' checks the status of a crawl job and returns status and progress information. The description explicitly states it retrieves status data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access firecrawl_check_crawl_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Firecrawl Web Scraping Server, and nothing reaches the server without passing your rules. This is the rule we recommend for firecrawl_check_crawl_status:
{
"version": "1",
"default": "deny",
"tools": {
"firecrawl_check_crawl_status": {}
}
}firecrawl_check_crawl_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of a crawl job. Usage Example: json { "name": "firecrawl_check_crawl_status", "arguments": { "id": "550e8400-e29b-41d4-a716-446655440000" } } Returns: Status and progress of the crawl job, including results if available. It is categorised as a Read tool in the Firecrawl Web Scraping Server MCP Server, which means it retrieves data without modifying state.
firecrawl_check_crawl_status accepts 1 parameter: id. The full parameter table on this page comes from the server's own tool schema.
Register the Firecrawl Web Scraping Server MCP server in PolicyLayer and add a rule for firecrawl_check_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 Web Scraping Server. Nothing to install.
firecrawl_check_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_check_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_check_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_check_crawl_status is provided by the Firecrawl Web Scraping Server MCP server (0xzapata/firecrawl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Firecrawl Web Scraping Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Firecrawl Web Scraping Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.