[STATELESS] Auto-detect and handle different content types (HTML, sitemap, RSS, text). Use when: URL type is unknown, crawling feeds/sitemaps, or want automatic format handling. Adapts strategy based on content. Creates new browser each time. For persistent operations use create_session + crawl.
AI agents call smart_crawl to retrieve information from MCP Server for Crawl4AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and processes web content but does not modify, delete, or execute arbitrary commands. While browser automation is involved, the stated purpose is content extraction and format detection, not execution of external operations. The tool adapts its crawling strategy based on content type but remains fundamentally a Read operation.
From the tool's definition Tool description states it 'auto-detect and handle different content types' and 'crawl feeds/sitemaps' with 'automatic format handling'.
Documented attack patterns abuse exactly the kind of access smart_crawl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Crawl4AI, and nothing reaches the server without passing your rules. This is the rule we recommend for smart_crawl:
{
"version": "1",
"default": "deny",
"tools": {
"smart_crawl": {}
}
} smart_crawl is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[STATELESS] Auto-detect and handle different content types (HTML, sitemap, RSS, text). Use when: URL type is unknown, crawling feeds/sitemaps, or want automatic format handling. Adapts strategy based on content. Creates new browser each time. For persistent operations use create_session + crawl. It is categorised as a Read tool in the MCP Server for Crawl4AI MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Crawl4AI MCP server in PolicyLayer and add a rule for smart_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 Server for Crawl4AI. Nothing to install.
smart_crawl 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 smart_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 smart_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.
smart_crawl is provided by the MCP Server for Crawl4AI MCP server (omgwtfwow/mcp-crawl4ai-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Crawl4AI, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP Server for Crawl4AI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.