edit_project
Update Studio Project. Spends ElevenLabs credits.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/edit-project.md
What edit_project does on Elevenlabs
AI agents use edit_project 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 | The name of the Studio project, used for identification only. |
title | string | null | — | |
author | string | null | — | |
project_id | string | Yes | The ID of the Studio project. |
isbn_number | string | null | — | |
volume_normalization | boolean | — | When the Studio project is downloaded, should the returned audio have postprocessing in order to make it compliant with audiobook normalized volume requirements |
default_title_voice_id | string | Yes | The voice_id that corresponds to the default voice used for new titles. |
default_paragraph_voice_id | string | Yes | The voice_id that corresponds to the default voice used for new paragraphs. |
Parameters from the server's own tool schema.
Why edit_project is rated Medium
An AI agent can call edit_project 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 edit_project 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 edit_project, this is the rule to start with:
edit_project 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 edit_project call is checked against it from then on.
Questions about edit_project
Update Studio Project. Spends ElevenLabs credits. 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.
edit_project accepts 8 parameters: name, title, author, project_id, isbn_number, volume_normalization, default_title_voice_id, default_paragraph_voice_id. Required: name, project_id, default_title_voice_id, default_paragraph_voice_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 edit_project: 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.
edit_project 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 edit_project 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 edit_project. 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.
edit_project 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