StartHealthCheckBackup · Veeam VBR v13 MCP Server MCP

WHAT IT DOES

What StartHealthCheckBackup does on Veeam VBR v13 MCP Server

AI agents invoke StartHealthCheckBackup 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 StartHealthCheckBackup needs a policy

Health check and repair operations are Execute category because they trigger backend processes that modify backup integrity state. Severity is high due to the blast radius: if an AI agent misuses this on critical backups, it could corrupt recovery data or consume significant infrastructure resources during repair. The tool is part of a backup/replication system where operational safety is paramount.

From the tool's definition 'Run a health check and repair operation on backups' indicates the tool triggers an active operation that repairs backup data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

StartHealthCheckBackup Rate-limited

StartHealthCheckBackup 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": {
    "StartHealthCheckBackup": {
      "limits": [
        {
          "counter": "starthealthcheckbackup_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 StartHealthCheckBackup

What does the StartHealthCheckBackup tool do? +

Run a health check and repair operation on backups. 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 StartHealthCheckBackup? +

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

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

Can I rate-limit StartHealthCheckBackup? +

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

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

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