Start a web crawl job. Crawls pages under the given URL path and converts them to markdown. Returns a job ID for tracking progress with crawl_status.
AI agents invoke crawl_start to trigger actions in UnWeb 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.
This tool initiates an active crawling operation that fetches multiple external web pages and processes them. It triggers an ongoing external operation (a crawl job) whose scope and effects depend on the URL argument provided. This goes beyond a simple read/fetch of a single resource — it spawns a background job that can touch many pages, consuming bandwidth and external server resources.
From the tool's definition 'Start a web crawl job. Crawls pages under the given URL path and converts them to markdown. Returns a job ID for tracking progress'
Attacks that exploit this kind of access
Start a web crawl job. Crawls pages under the given URL path and converts them to markdown. Returns a job ID for tracking progress with crawl_status. It is categorised as a Execute tool in the UnWeb MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UnWeb MCP Server MCP server in PolicyLayer and add a rule for crawl_start: 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 UnWeb MCP Server. Nothing to install.
crawl_start 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 crawl_start 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 crawl_start. 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.
crawl_start is provided by the UnWeb MCP Server MCP server (mbsoft-systems/unweb-mcp). 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 →