search_and_crawl · Crawl4AI MCP Server MCP: Risk & Policy

WHAT IT DOES

What search_and_crawl does on Crawl4AI MCP Server

AI agents invoke search_and_crawl to trigger actions in Crawl4AI MCP 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.

WHY IT NEEDS A POLICY

Why search_and_crawl needs a policy

Based on the tool name and sibling tools (batch_search_google, crawl_url, deep_crawl_site), this tool likely combines a Google search with subsequent web crawling — triggering external network operations against potentially many URLs. This spans Read and Execute; since it actively triggers external operations (network requests, JavaScript execution per server description), Execute is the most appropriate category.

From the tool's definition Tool name 'search_and_crawl' combined with server description mentioning Google search integration and web crawling capabilities; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

search_and_crawl Rate-limited

search_and_crawl stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_and_crawl": {
      "limits": [
        {
          "counter": "search_and_crawl_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Crawl4AI MCP Server, so you can run agents against it safely.

FAQ

Questions about search_and_crawl

What does the search_and_crawl tool do? +

search_and_crawl. It is categorised as a Execute tool in the Crawl4AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on search_and_crawl? +

Register the Crawl4AI MCP Server MCP server in PolicyLayer and add a rule for search_and_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 Crawl4AI MCP Server. Nothing to install.

What risk level is search_and_crawl? +

search_and_crawl is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit search_and_crawl? +

Yes. Add a rate_limit block to the search_and_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.

How do I block search_and_crawl completely? +

Set action: deny in the PolicyLayer policy for search_and_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.

What MCP server provides search_and_crawl? +

search_and_crawl is provided by the Crawl4AI MCP Server MCP server (sruckh/crawl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.