Crawl a website recursively via BFS from a starting URL to configurable depth. Returns all discovered URLs with metadata, page titles, and optionally page content + extracted fields inline.\n\nWHEN TO USE: Full-site scraping, sitemap generation, content indexing, competitive analysis — when you n...
AI agents invoke novada_proxy_crawl to trigger actions in Novada Proxy. 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 recursive crawling operation across an entire website, making potentially hundreds or thousands of HTTP requests through residential proxy IPs to bypass anti-bot systems. The operation is not a simple read — it triggers an automated, multi-step external process (BFS traversal, configurable depth, proxy routing) whose scope and side effects depend on arguments.
From the tool's definition Crawl a website recursively via BFS from a starting URL to configurable depth... Full-site scraping, sitemap generation, content indexing, competitive analysis — when you need MORE than a single page.
Attacks that exploit this kind of access
Crawl a website recursively via BFS from a starting URL to configurable depth. Returns all discovered URLs with metadata, page titles, and optionally page content + extracted fields inline.\n\nWHEN TO USE: Full-site scraping, sitemap generation, content indexing, competitive analysis — when you need MORE than a single page.\nUSE novada_proxy_map INSTEAD IF: You only need links from ONE page.\nUSE novada_proxy_batch_fetch INSTEAD IF: You already have the URLs and just need content.\nWORKFLOW: crawl(url, max_pages=20, max_depth=3, include_content=true) → get full site content in one call.\nFILTERING: Use include_patterns/exclude_patterns to control which URLs are followed (e.g. include_patterns:[. It is categorised as a Execute tool in the Novada Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Novada Proxy MCP server in PolicyLayer and add a rule for novada_proxy_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 Novada Proxy. Nothing to install.
novada_proxy_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 novada_proxy_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 novada_proxy_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.
novada_proxy_crawl is provided by the Novada Proxy MCP server (novadalabs/novada-proxy). 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 →