deep_crawl_site · Crawl4AI MCP Server MCP: Risk & Policy

WHAT IT DOES

What deep_crawl_site does on Crawl4AI MCP Server

AI agents invoke deep_crawl_site 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 deep_crawl_site needs a policy

Based on the tool name and server context, this tool likely performs deep/recursive crawling of an entire website, which involves executing network requests, potentially running JavaScript, and consuming significant resources. Sibling tools like 'crawl_url' and 'batch_crawl' confirm the pattern. Empty description lowers confidence.

From the tool's definition Tool name 'deep_crawl_site' combined with server description mentioning 'advanced web crawling' with 'JavaScript support'. Description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deep_crawl_site Rate-limited

deep_crawl_site 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": {
    "deep_crawl_site": {
      "limits": [
        {
          "counter": "deep_crawl_site_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 deep_crawl_site

What does the deep_crawl_site tool do? +

deep_crawl_site. 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 deep_crawl_site? +

Register the Crawl4AI MCP Server MCP server in PolicyLayer and add a rule for deep_crawl_site: 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 deep_crawl_site? +

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

Can I rate-limit deep_crawl_site? +

Yes. Add a rate_limit block to the deep_crawl_site 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 deep_crawl_site completely? +

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

deep_crawl_site 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.