ViVMSnapshotReplicaPlannedFailover

WHAT IT DOES

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 IT NEEDS A POLICY

Why ViVMSnapshotReplicaPlannedFailover needs a policy

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…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ViVMSnapshotReplicaPlannedFailover Rate-limited

ViVMSnapshotReplicaPlannedFailover 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": {
    "ViVMSnapshotReplicaPlannedFailover": {
      "limits": [
        {
          "counter": "vivmsnapshotreplicaplannedfailover_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 ViVMSnapshotReplicaPlannedFailover

What does the ViVMSnapshotReplicaPlannedFailover tool do? +

Start planned 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 ViVMSnapshotReplicaPlannedFailover? +

Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for ViVMSnapshotReplicaPlannedFailover: 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 ViVMSnapshotReplicaPlannedFailover? +

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

Can I rate-limit ViVMSnapshotReplicaPlannedFailover? +

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

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

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