sound_generation
Sound Generation. Spends ElevenLabs credits. Returns audio/mpeg bytes; pass output_path to save them.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/sound-generation.md
What sound_generation does on Elevenlabs
AI agents use sound_generation 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 |
|---|---|---|---|
loop | boolean | — | Whether to create a sound effect that loops smoothly. Only available for the 'eleven_text_to_sound_v2 model'. |
text | string | Yes | The text that will get converted into a sound effect. |
model_id | string | — | |
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). |
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 |
duration_seconds | number | null | — | |
prompt_influence | number | null | — |
Parameters from the server's own tool schema.
Why sound_generation is rated Medium
An AI agent can call sound_generation 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 sound_generation 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 sound_generation, this is the rule to start with:
sound_generation 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 sound_generation call is checked against it from then on.
Questions about sound_generation
Sound Generation. 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.
sound_generation accepts 7 parameters: loop, text, model_id, output_path, output_format, duration_seconds, prompt_influence. Required: text. 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 sound_generation: 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.
sound_generation 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 sound_generation 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 sound_generation. 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.
sound_generation 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