New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

DeleteGlobalVMExclusion

Remove a VM from the global exclusion list.

SERVERVeeam VBR v13 MCP Server SOURCEkid-boy/veeam-mcp-13
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kid-boy-veeam-mcp-13/deleteglobalvmexclusion.md

What DeleteGlobalVMExclusion does on Veeam VBR v13 MCP Server

AI agents call DeleteGlobalVMExclusion 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 DeleteGlobalVMExclusion is rated Critical

This tool deletes a VM entry from the global exclusion list in Veeam Backup & Replication. Removing a VM from the exclusion list means it will now be included in backup jobs globally, which could have significant unintended consequences (e.g., unexpected backup jobs running, storage consumption, or policy violations).

From the tool's definition 'Remove a VM from the global exclusion list' — permanently removes a configuration entry; 'Delete' prefix indicates irreversible deletion

Questions about DeleteGlobalVMExclusion

What does the DeleteGlobalVMExclusion tool do? +

Remove a VM from the global exclusion list. 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.

How do I enforce a policy on DeleteGlobalVMExclusion? +

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

DeleteGlobalVMExclusion is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit DeleteGlobalVMExclusion? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Veeam VBR v13 MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.