rename_replica · Tavus MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_replica does on Tavus MCP Server

AI agents use rename_replica to create or update resources in Tavus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tavus MCP Server environment.

WHY IT NEEDS A POLICY

Why rename_replica needs a policy

This is a Write action because it modifies a replica's name/properties, which is reversible and does not destroy data or execute arbitrary code. The severity is medium because renaming a replica could affect workflows or integrations that reference the replica by name, potentially causing confusion or operational disruption, though the change itself is easily undone.

From the tool's definition Tool name is 'rename_replica' and description states 'Rename an existing replica'. Renaming modifies metadata/configuration of an existing resource reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_replica Rate-limited

rename_replica 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_replica": {
      "limits": [
        {
          "counter": "rename_replica_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tavus MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_replica

What does the rename_replica tool do? +

Rename an existing replica. It is categorised as a Write tool in the Tavus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_replica? +

Register the Tavus MCP Server MCP server in PolicyLayer and add a rule for rename_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.

What risk level is rename_replica? +

rename_replica is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_replica? +

Yes. Add a rate_limit block to the rename_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.

How do I block rename_replica completely? +

Set action: deny in the PolicyLayer policy for rename_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.

What MCP server provides rename_replica? +

rename_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.