Start an asynchronous crawl of multiple pages from a starting URL.
AI agents invoke firecrawl_crawl to trigger actions in Mcp Registry Registry. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (web crawling) whose effects depend on the URL argument provided. While crawling itself is not destructive to the target or user data, it is a proactive operation that traverses and retrieves data from external systems, and could be misused to crawl private/sensitive sites, protected resources, or generate harmful traffic.
From the tool's definition Tool starts an asynchronous crawl of multiple pages from a starting URL - 'crawl' is an active operation that triggers external web scraping/crawling.
Attacks that exploit this kind of access
Start an asynchronous crawl of multiple pages from a starting URL. It is categorised as a Execute tool in the Mcp Registry Registry MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Registry Registry MCP server in PolicyLayer and add a rule for firecrawl_crawl: 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 Mcp Registry Registry. Nothing to install.
firecrawl_crawl is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the firecrawl_crawl 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. 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 is provided by the Mcp Registry Registry MCP server (@mastra/mcp-registry-registry). 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 →