text_to_voice
[Deprecated] Generate A Voice Preview From Description. Spends ElevenLabs credits. Deprecated upstream.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/text-to-voice.md
What text_to_voice does on Elevenlabs
AI agents call text_to_voice to retrieve information from Elevenlabs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
seed | number | null | — | |
text | string | null | — | |
quality | number | — | Higher quality results in better voice output but less variety. |
loudness | number | — | Controls the volume level of the generated voice. -1 is quietest, 1 is loudest, 0 corresponds to roughly -24 LUFS. |
output_format | string | — | Output format of the generated audio. Formatted as codec_sample_rate_bitrate. So an mp3 with 22.05kHz sample rate at 32kbs is represented as mp3_22050_32. MP3 w |
guidance_scale | number | — | Controls how closely the AI follows the prompt. Lower numbers give the AI more freedom to be creative, while higher numbers force it to stick more to the prompt |
should_enhance | boolean | — | Whether to enhance the voice description using AI to add more detail and improve voice generation quality. When enabled, the system will automatically expand si |
voice_description | string | Yes | Description to use for the created voice. |
auto_generate_text | boolean | — | Whether to automatically generate a text suitable for the voice description. |
Parameters from the server's own tool schema.
Why text_to_voice is rated Low
Even though text_to_voice only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs text_to_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 text_to_voice, this is the rule to start with:
text_to_voice is read-only, so it stays allowed. 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 text_to_voice call is checked against it from then on.
Questions about text_to_voice
[Deprecated] Generate A Voice Preview From Description. Spends ElevenLabs credits. Deprecated upstream. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
text_to_voice accepts 9 parameters: seed, text, quality, loudness, output_format, guidance_scale, should_enhance, voice_description, auto_generate_text. Required: voice_description. 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 text_to_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.
text_to_voice is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the text_to_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 text_to_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.
text_to_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