ViVMSnapshotReplicaPermanentFailover

WHAT IT DOES

What ViVMSnapshotReplicaPermanentFailover does on Veeam VBR v13 MCP Server

AI agents invoke ViVMSnapshotReplicaPermanentFailover to trigger actions in Veeam VBR v13 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ViVMSnapshotReplicaPermanentFailover needs a policy

While 'permanent failover' might seem destructive, it is fundamentally an Execute action: it triggers a complex orchestration operation (failover) whose effects depend on the replica state and infrastructure configuration, rather than directly deleting or overwriting data.

From the tool's definition ViVMSnapshotReplicaPermanentFailover starts a permanent failover operation for VMware vSphere snapshot replicas.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ViVMSnapshotReplicaPermanentFailover Rate-limited

ViVMSnapshotReplicaPermanentFailover stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ViVMSnapshotReplicaPermanentFailover": {
      "limits": [
        {
          "counter": "vivmsnapshotreplicapermanentfailover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about ViVMSnapshotReplicaPermanentFailover

What does the ViVMSnapshotReplicaPermanentFailover tool do? +

Start permanent failover for a VMware vSphere snapshot replica. It is categorised as a Execute tool in the Veeam VBR v13 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ViVMSnapshotReplicaPermanentFailover? +

Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for ViVMSnapshotReplicaPermanentFailover: 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 Veeam VBR v13 MCP Server. Nothing to install.

What risk level is ViVMSnapshotReplicaPermanentFailover? +

ViVMSnapshotReplicaPermanentFailover is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ViVMSnapshotReplicaPermanentFailover? +

Yes. Add a rate_limit block to the ViVMSnapshotReplicaPermanentFailover 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 ViVMSnapshotReplicaPermanentFailover completely? +

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

ViVMSnapshotReplicaPermanentFailover is provided by the Veeam VBR v13 MCP Server MCP server (kid-boy/veeam-mcp-13). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.