ViVMSnapshotReplicaPlannedFailover

What ViVMSnapshotReplicaPlannedFailover does on Veeam VBR v13 MCP Server

AI agents invoke ViVMSnapshotReplicaPlannedFailover 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 ViVMSnapshotReplicaPlannedFailover is rated High

Failover operations are Execute-category because they trigger external system state transitions with significant blast radius. While reversible (failback is possible), initiating failover without proper safeguards could cause unintended VM migration, service disruption, or data consistency issues. This is critical severity because it affects production infrastructure availability and continuity.

From the tool's definition Tool name is 'ViVMSnapshotReplicaPlannedFailover' and description states it 'Start[s] planned failover for a VMware vSphere snapshot replica.' Failover is an active operational trigger that initiates infrastructure state changes whose effects depend on…

The rule that runs ViVMSnapshotReplicaPlannedFailover safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Veeam VBR v13 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ViVMSnapshotReplicaPlannedFailover, this is the rule to start with:

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

Questions about ViVMSnapshotReplicaPlannedFailover