Delete a replica permanently
AI agents call delete_replica 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 a replica, which is an irreversible action that destroys data. Destructive actions have higher severity than Write (which are reversible modifications). The blast radius is high because an AI agent misusing this tool could permanently remove important replica assets without recovery options.
From the tool's definition Tool name is 'delete_replica' and description states 'Delete a replica permanently'. The word 'permanently' indicates the action is irreversible and cannot be undone.
Attacks that exploit this kind of access
Delete a replica 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_replica: 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_replica 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_replica 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_replica. 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_replica 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 →