Start an asynchronous crawl of multiple pages from a starting URL.
AI agents invoke firecrawl_crawl to trigger actions in Mcp Docs Server. 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 a web crawling operation whose effects depend on the target URL argument. While it retrieves data (Read-like behavior), the mechanism involves triggering an external crawl process that consumes resources and sends requests to third-party servers, making it an Execute action. It is not Destructive, Write, or Financial.
From the tool's definition Tool performs an asynchronous crawl operation that triggers external web scraping against arbitrary URLs specified by the user.
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 Docs Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Docs Server 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 Docs Server. 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 Docs Server MCP server (@mastra/mcp-docs-server). 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 →