post_agent_hold_audio_route
Post Agent Hold Audio.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/post-agent-hold-audio-route.md
What post_agent_hold_audio_route does on Elevenlabs
AI agents use post_agent_hold_audio_route 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 |
|---|---|---|---|
agent_id | string | Yes | The id of an agent. This is returned on agent creation. |
hold_audio_file_path | string | — | An MP3 or WAV file played on loop to callers waiting in the agent's concurrency wait queue. Maximum size 40 MB, maximum duration 180 seconds. Local path. Requir |
hold_audio_file_base64 | string | — | Base64 contents for "hold_audio_file". Use this when the server cannot read your local disk. |
hold_audio_file_filename | string | — | Filename to send for "hold_audio_file". Some endpoints infer the audio format from it. |
Parameters from the server's own tool schema.
Why post_agent_hold_audio_route is rated Medium
An AI agent can call post_agent_hold_audio_route 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 post_agent_hold_audio_route 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 post_agent_hold_audio_route, this is the rule to start with:
post_agent_hold_audio_route 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 post_agent_hold_audio_route call is checked against it from then on.
Questions about post_agent_hold_audio_route
Post Agent Hold Audio. 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.
post_agent_hold_audio_route accepts 4 parameters: agent_id, hold_audio_file_path, hold_audio_file_base64, hold_audio_file_filename. Required: agent_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 post_agent_hold_audio_route: 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.
post_agent_hold_audio_route 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 post_agent_hold_audio_route 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 post_agent_hold_audio_route. 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.
post_agent_hold_audio_route 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