Delete a quick-cloned custom voice by voice ID
AI agents call delete_cloned_voice to permanently remove resources in Typecast API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes user-created voice data with no ability to undo the operation. While the blast radius is limited to voice assets rather than critical systems, the irreversible nature of deletion and potential loss of user work warrants the Destructive category and high severity rating.
From the tool's definition Tool name contains 'delete' and description states 'Delete a quick-cloned custom voice by voice ID', which irreversibly removes a user-created voice asset.
Attacks that exploit this kind of access
Delete a quick-cloned custom voice by voice ID. It is categorised as a Destructive tool in the Typecast API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Typecast API MCP Server MCP server in PolicyLayer and add a rule for delete_cloned_voice: 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 Typecast API MCP Server. Nothing to install.
delete_cloned_voice 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_cloned_voice 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_cloned_voice. 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_cloned_voice is provided by the Typecast API MCP Server MCP server (neosapience/typecast-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →