RevokeCapacityLicense
Revoke a capacity license from an unstructured data workload.
This record as markdown: /tools/kid-boy-veeam-mcp-13/revokecapacitylicense.md
What RevokeCapacityLicense does on Veeam VBR v13 MCP Server
AI agents call RevokeCapacityLicense to permanently remove resources in Veeam VBR v13 MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why RevokeCapacityLicense is rated Critical
Revoking a license is not simply a write/update; it removes an assigned right and cannot be undone without re-assigning a license. This is an irreversible removal action, placing it in the Destructive category. The blast radius is high because misuse could disable backup protection for entire unstructured data workloads.
From the tool's definition 'Revoke a capacity license from an unstructured data workload' — revoking a license removes an assigned entitlement, which is an irreversible action that immediately disables the licensed capability for the target workload.
Attacks that exploit this kind of access
The rule that runs RevokeCapacityLicense 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 RevokeCapacityLicense, this is the rule to start with:
RevokeCapacityLicense is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every RevokeCapacityLicense call is checked against it from then on.
Questions about RevokeCapacityLicense
Revoke a capacity license from an unstructured data workload. It is categorised as a Destructive tool in the Veeam VBR v13 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for RevokeCapacityLicense: 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.
RevokeCapacityLicense is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the RevokeCapacityLicense 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.
Set action: deny in the PolicyLayer policy for RevokeCapacityLicense. 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.
RevokeCapacityLicense 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.
More on Veeam VBR v13 MCP Server, and thousands of servers like it.
Across the catalogue