text_to_dialogue

Text To Dialogue (Multi-Voice) Spends ElevenLabs credits. Returns audio/mpeg bytes; pass output_path to save them.

SERVERElevenlabs SOURCE@aiwerk/mcp-server-elevenlabs

Medium RISK CLASS

Category Write

Parameters 101 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/text-to-dialogue.md

WHAT IT DOES

What text_to_dialogue does on Elevenlabs

AI agents use text_to_dialogue 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
`seed`	number \| null	—
`inputs`	array	Yes	A list of dialogue inputs, each containing text and a voice ID which will be converted into speech. The maximum number of unique voice IDs is 10. For reliable g
`model_id`	string	—	Identifier of the model that will be used, you can query them using GET /v1/models. The model needs to have support for text to speech, you can check this using
`settings`	object	—
`output_path`	string	—	Where to write the returned bytes. Relative paths resolve against ELEVENLABS_OUTPUT_DIR. Omit it to get the data inline as base64 (small files only).
`language_code`	string \| null	—
`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
`enable_logging`	boolean	—	When enable_logging is set to false zero retention mode will be used for the request. This will mean history features are unavailable for this request, includin
`apply_text_normalization`	string	—	This parameter controls text normalization with three modes: 'auto', 'on', and 'off'. When set to 'auto', the system will automatically decide whether to apply
`pronunciation_dictionary_locators`	object	—

Parameters from the server's own tool schema.

RISK

Why text_to_dialogue is rated Medium

An AI agent can call text_to_dialogue 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 signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs text_to_dialogue 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_dialogue, this is the rule to start with:

text_to_dialogue Rate-limited

text_to_dialogue 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "text_to_dialogue": {
      "limits": [
        {
          "counter": "text_to_dialogue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every text_to_dialogue call is checked against it from then on.

FAQ

Questions about text_to_dialogue

What does the text_to_dialogue tool do? +

Text To Dialogue (Multi-Voice) Spends ElevenLabs credits. Returns audio/mpeg bytes; pass output_path to save them. 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.

What parameters does text_to_dialogue accept? +

text_to_dialogue accepts 10 parameters: seed, inputs, model_id, settings, output_path, language_code, output_format, enable_logging, apply_text_normalization, pronunciation_dictionary_locators. Required: inputs. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on text_to_dialogue? +

Register the Elevenlabs MCP server in PolicyLayer and add a rule for text_to_dialogue: 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.

What risk level is text_to_dialogue? +

text_to_dialogue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit text_to_dialogue? +

Yes. Add a rate_limit block to the text_to_dialogue 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.

How do I block text_to_dialogue completely? +

Set action: deny in the PolicyLayer policy for text_to_dialogue. 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.

What MCP server provides text_to_dialogue? +

text_to_dialogue 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.

KEEP EXPLORING

More on Elevenlabs, and thousands of servers like it.

This server

All 390 Elevenlabs tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →