Delete a speech permanently
AI agents call delete_speech to permanently remove resources in Tavus 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 speech data without the ability to recover it. Destructive operations that irreversibly remove data pose a high risk if an AI agent misuses them, as they could delete important content. The presence of sibling destructive tools (delete_conversation, delete_lipsync, delete_persona, delete_replica, delete_video) on the same server confirms this classification pattern.
From the tool's definition Tool name 'delete_speech' combined with description 'Delete a speech permanently' indicates irreversible deletion of data. The word 'permanently' confirms the action cannot be undone.
Attacks that exploit this kind of access
Delete a speech permanently. It is categorised as a Destructive tool in the Tavus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tavus MCP Server MCP server in PolicyLayer and add a rule for delete_speech: 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 Tavus MCP Server. Nothing to install.
delete_speech 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_speech 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_speech. 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_speech is provided by the Tavus MCP Server MCP server (rakeshdavid/tavus-mcp). 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 →