Search and retrieve content from web pages with optional scraping.
AI agents call firecrawl_search to retrieve information from Firecrawl MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs search and content retrieval from web pages without modifying, deleting, or executing code. It falls squarely into the Read category as a query/fetch operation with no side effects on the target data. The blast radius is low since it only accesses publicly available web content.
From the tool's definition Tool name 'firecrawl_search' and description 'Search and retrieve content from web pages' indicate data retrieval operations. The phrase 'with optional scraping' refers to extracting existing web content, not modifying or deleting it.
Attacks that exploit this kind of access
Search and retrieve content from web pages with optional scraping. It is categorised as a Read tool in the Firecrawl MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firecrawl MCP Server MCP server in PolicyLayer and add a rule for firecrawl_search: 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 MCP Server. Nothing to install.
firecrawl_search 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_search 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_search. 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_search is provided by the Firecrawl MCP Server MCP server (mcma123/firecrawl-mcp-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 →