create_file_document_route
Create File Document.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/create-file-document-route.md
What create_file_document_route does on Elevenlabs
AI agents use create_file_document_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 |
|---|---|---|---|
name | string | null | — | A custom, human-readable name for the document. |
file_path | string | — | Documentation that the agent will have access to in order to interact with users. Local path. Required for this call. |
file_base64 | string | — | Base64 contents for "file". Use this when the server cannot read your local disk. |
file_filename | string | — | Filename to send for "file". Some endpoints infer the audio format from it. |
parent_folder_id | string | null | — | If set, the created document or folder will be placed inside the given folder. |
Parameters from the server's own tool schema.
Why create_file_document_route is rated Medium
An AI agent can call create_file_document_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 file system path (file_path)
Attacks that exploit this kind of access
The rule that runs create_file_document_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_file_document_route, this is the rule to start with:
create_file_document_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_file_document_route call is checked against it from then on.
Questions about create_file_document_route
Create File Document. 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_file_document_route accepts 5 parameters: name, file_path, file_base64, file_filename, parent_folder_id. 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_file_document_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_file_document_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_file_document_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_file_document_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_file_document_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