get_audio_from_sample
Get Audio From Sample. Returns audio/* bytes; pass output_path to save them.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/get-audio-from-sample.md
What get_audio_from_sample does on Elevenlabs
AI agents call get_audio_from_sample 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 |
|---|---|---|---|
voice_id | string | Yes | Voice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices. |
sample_id | string | Yes | Sample ID to be used, you can use GET https://api.elevenlabs.io/v1/voices/{voice_id} to list all the available samples for a voice. |
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). |
Parameters from the server's own tool schema.
Why get_audio_from_sample is rated Low
Even though get_audio_from_sample 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 get_audio_from_sample 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 get_audio_from_sample, this is the rule to start with:
get_audio_from_sample 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 get_audio_from_sample call is checked against it from then on.
Questions about get_audio_from_sample
Get Audio From Sample. Returns audio/* bytes; pass output_path to save them. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
get_audio_from_sample accepts 3 parameters: voice_id, sample_id, output_path. Required: voice_id, sample_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 get_audio_from_sample: 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.
get_audio_from_sample 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 get_audio_from_sample 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 get_audio_from_sample. 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.
get_audio_from_sample 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