This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/add-from-file.md
What add_from_file does on Elevenlabs
AI agents use add_from_file 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 | Yes | The name of the pronunciation dictionary, used for identification only. |
file_path | string | — | A lexicon .pls file which we will use to initialize the project with. Local path. |
description | string | null | — | A description of the pronunciation dictionary, used for identification only. |
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. |
workspace_access | object | — | Should be one of 'admin', 'editor' or 'viewer'. If not provided, defaults to no access. |
Parameters from the server's own tool schema.
Why add_from_file is rated Medium
An AI agent can call add_from_file 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 add_from_file 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 add_from_file, this is the rule to start with:
add_from_file 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 add_from_file call is checked against it from then on.
Questions about add_from_file
Add A Pronunciation Dictionary. 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.
add_from_file accepts 6 parameters: name, file_path, description, file_base64, file_filename, workspace_access. Required: name. 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 add_from_file: 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.
add_from_file 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 add_from_file 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 add_from_file. 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.
add_from_file 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