This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/delete-project.md
What delete_project does on Elevenlabs
AI agents call delete_project to permanently remove resources in Elevenlabs, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | The ID of the Studio project. |
Parameters from the server's own tool schema.
Why delete_project is rated Critical
An AI agent that decides to call delete_project doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Elevenlabs is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_project, this is the rule to start with:
delete_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every delete_project call is checked against it from then on.
Questions about delete_project
Delete Studio Project. It is categorised as a Destructive tool in the Elevenlabs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_project accepts 1 parameter: project_id. Required: project_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 delete_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.
delete_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue