This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/create-crawl-job-route.md
What create_crawl_job_route does on Elevenlabs
AI agents use create_crawl_job_route to create or update resources in Elevenlabs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Elevenlabs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to a page of documentation that the agent will have access to in order to interact with users. |
pattern | string | null | — | |
max_depth | number | — | Maximum depth for crawling (1-5), defaults to 3. |
max_pages | number | — | Maximum number of pages to crawl (1-10,000), defaults to 1000. |
auto_remove | boolean | — | Whether to automatically remove the document if the URL becomes unavailable. Only applicable when auto-sync is enabled. |
sitemap_urls | object | — | |
enable_auto_sync | boolean | — | Whether to enable auto-sync for this URL document. |
parent_folder_id | string | null | — | |
minimum_frequency_days | number | null | — |
Parameters from the server's own tool schema.
Why create_crawl_job_route is rated Medium
An AI agent can call create_crawl_job_route faster than any human can review: one bad instruction and it creates or modifies resources in Elevenlabs by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs create_crawl_job_route safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_crawl_job_route, this is the rule to start with:
create_crawl_job_route stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every create_crawl_job_route call is checked against it from then on.
Questions about create_crawl_job_route
Create Crawl Job. It is categorised as a Write tool in the Elevenlabs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_crawl_job_route accepts 9 parameters: url, pattern, max_depth, max_pages, auto_remove, sitemap_urls, enable_auto_sync, parent_folder_id, minimum_frequency_days. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for create_crawl_job_route: 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 Elevenlabs. Nothing to install.
create_crawl_job_route is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_crawl_job_route 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 create_crawl_job_route. 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.
create_crawl_job_route is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue