edit_voice
A write tool on the Elevenlabs MCP server.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/edit-voice.md
What edit_voice does on Elevenlabs
AI agents use edit_voice 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 that identifies this voice. This will be displayed in the dropdown of the website. |
labels | object | — | Labels for the voice. Keys can be language, accent, gender, or age. |
voice_id | string | Yes | Voice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices. |
description | string | null | — | A description of the voice. |
files_paths | array | — | Audio files to add to the voice Local paths. |
files_filenames | array | — | Filenames to send for "files". Some endpoints infer the audio format from them. |
files_base64_list | array | — | Base64 contents for "files", one entry per file. Use this when the server cannot read your local disk. |
moderate_metadata | boolean | — | Run synchronous LLM moderation over the voice name and description when they change. Has no effect unless the voice_library_metadata_moderation feature flag is |
remove_background_noise | boolean | — | If set will remove background noise for voice samples using our audio isolation model. If the samples do not include background noise, it can make the quality w |
Parameters from the server's own tool schema.
Why edit_voice is rated Medium
An AI agent can call edit_voice 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.
Attacks that exploit this kind of access
The rule that runs edit_voice 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 edit_voice, this is the rule to start with:
edit_voice 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 edit_voice call is checked against it from then on.
Questions about edit_voice
edit_voice is a write tool on the Elevenlabs MCP server. 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.
edit_voice accepts 9 parameters: name, labels, voice_id, description, files_paths, files_filenames, files_base64_list, moderate_metadata, remove_background_noise. Required: name, voice_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 edit_voice: 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.
edit_voice 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 edit_voice 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 edit_voice. 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.
edit_voice 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