update_procedure_draft_route
Update Procedure Draft.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/update-procedure-draft-route.md
What update_procedure_draft_route does on Elevenlabs
AI agents use update_procedure_draft_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 |
|---|---|---|---|
name | string | Yes | Procedure name |
type | string | Yes | |
content | string | Yes | Procedure content |
trigger | string | null | — | |
agent_id | string | Yes | Agent ID to get the procedure draft from |
branch_id | string | Yes | Branch ID to get the procedure draft from |
procedure_id | string | Yes | The procedure ID |
Parameters from the server's own tool schema.
Why update_procedure_draft_route is rated Medium
An AI agent can call update_procedure_draft_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.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs update_procedure_draft_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 update_procedure_draft_route, this is the rule to start with:
update_procedure_draft_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 update_procedure_draft_route call is checked against it from then on.
Questions about update_procedure_draft_route
Update Procedure Draft. 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_procedure_draft_route accepts 7 parameters: name, type, content, trigger, agent_id, branch_id, procedure_id. Required: name, type, content, agent_id, branch_id, procedure_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 update_procedure_draft_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.
update_procedure_draft_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 update_procedure_draft_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 update_procedure_draft_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.
update_procedure_draft_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