update_speech_engine
A write tool on the Elevenlabs MCP server.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/update-speech-engine.md
What update_speech_engine does on Elevenlabs
AI agents use update_speech_engine 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 |
|---|---|---|---|
asr | object | — | |
tts | object | — | |
vad | object | — | |
name | string | null | — | |
tags | object | — | |
turn | object | — | |
privacy | object | — | |
language | string | null | — | |
overrides | object | — | |
call_limits | object | — | |
conversation | object | — | |
speech_engine | object | — |
Parameters from the server's own tool schema.
Why update_speech_engine is rated Medium
An AI agent can call update_speech_engine 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 (13 properties)
Attacks that exploit this kind of access
The rule that runs update_speech_engine 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 update_speech_engine, this is the rule to start with:
update_speech_engine 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 update_speech_engine call is checked against it from then on.
Questions about update_speech_engine
update_speech_engine is a write tool on the Elevenlabs MCP server. 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.
update_speech_engine accepts 12 parameters: asr, tts, vad, name, tags, turn, privacy, language, overrides, call_limits, conversation, speech_engine. 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 update_speech_engine: 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.
update_speech_engine 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 update_speech_engine 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 update_speech_engine. 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.
update_speech_engine 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