# DisableProtectionGroup

Disable a protection group.

Agent View of the PolicyLayer registry record for `DisableProtectionGroup`. HTML page: https://policylayer.com/tools/kid-boy-veeam-mcp-13/disableprotectiongroup

## Facts

- Tool: `DisableProtectionGroup`
- Server: Veeam VBR v13 MCP Server (`kid-boy/veeam-mcp-13`) — https://policylayer.com/tools/kid-boy-veeam-mcp-13.md
- Homepage: https://github.com/kid-boy/veeam-mcp-13
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "DisableProtectionGroup",
    "arguments": {}
  }
}
```

## Why DisableProtectionGroup is rated Medium

This tool modifies the operational state of a protection group by disabling it, which is a Write operation (reversible change to system configuration). It is severe (high) because disabling protection groups halts backup operations, leaving systems unprotected and potentially exposing them to data loss if failure occurs during the disabled period.

From the tool's own definition: "DisableProtectionGroup disables a protection group—a reversible configuration change that modifies the active state of backup protection without deleting underlying data or infrastructure."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Veeam VBR v13 MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "DisableProtectionGroup": {
      "limits": [
        {
          "counter": "disableprotectiongroup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Veeam VBR v13 MCP Server (327)

- `clearAgentPolicyCache` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/clearagentpolicycache.md
- `DeleteBackup` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletebackup.md
- `DeleteBackupObject` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletebackupobject.md
- `DeleteCloudCreds` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletecloudcreds.md
- `DeleteCloudCredsHelperApplianceAsync` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletecloudcredshelperapplianceasync.md
- `DeleteComputerRecoveryToken` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletecomputerrecoverytoken.md
- `DeleteCreds` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletecreds.md
- `DeleteDatastoreLatencySettings` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletedatastorelatencysettings.md
- `DeleteEncryptionPassword` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteencryptionpassword.md
- `DeleteEntraIDTenants` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteentraidtenants.md
- `DeleteGlobalVMExclusion` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteglobalvmexclusion.md
- `DeleteJob` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletejob.md
- `DeleteKMSServer` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletekmsserver.md
- `DeleteManagedServer` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletemanagedserver.md
- `DeleteProtectionGroup` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteprotectiongroup.md
- `DeleteProxy` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteproxy.md
- `DeleteRepository` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleterepository.md
- `DeleteScaleOutRepository` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deletescaleoutrepository.md
- `DeleteUnstructuredDataServers` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteunstructureddataservers.md
- `DeleteUser` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/deleteuser.md
- `RemoveInstanceLicense` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/removeinstancelicense.md
- `RemoveLicense` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/removelicense.md
- `ResetAllBestPracticesComplianceStatuses` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/resetallbestpracticescompliancestatuses.md
- `ResetBestPracticesComplianceStatus` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/resetbestpracticescompliancestatus.md
- `RevokeCapacityLicense` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/revokecapacitylicense.md
- `RevokeInstanceLicense` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/revokeinstancelicense.md
- `RevokeSocketLicense` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/revokesocketlicense.md
- `UninstallAgentFromDiscoveredEntities` — Destructive — https://policylayer.com/tools/kid-boy-veeam-mcp-13/uninstallagentfromdiscoveredentities.md
- `applyAgentPolicyConfiguration` — Execute — https://policylayer.com/tools/kid-boy-veeam-mcp-13/applyagentpolicyconfiguration.md
- `AzureInstantVMRecoveryMigrate` — Execute — https://policylayer.com/tools/kid-boy-veeam-mcp-13/azureinstantvmrecoverymigrate.md
- …and 297 more: https://policylayer.com/tools/kid-boy-veeam-mcp-13.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=kid-boy-veeam-mcp-13 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/kid-boy-veeam-mcp-13