GetGlobalVMExclusion

Get a specific global VM exclusion by ID.

SERVERVeeam VBR v13 MCP Server SOURCEkid-boy/veeam-mcp-13

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What GetGlobalVMExclusion does on Veeam VBR v13 MCP Server

AI agents call GetGlobalVMExclusion to retrieve information from Veeam VBR v13 MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why GetGlobalVMExclusion is rated Low

This tool retrieves configuration data about a global VM exclusion setting by its identifier. It is a read-only query operation that does not modify, delete, or execute any actions—only fetches existing information. The blast radius of misuse is minimal, as an agent could at worst discover exclusion policies but cannot alter them or cause operational impact.

From the tool's definition Tool name 'GetGlobalVMExclusion' and description 'Get a specific global VM exclusion by ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GetGlobalVMExclusion 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 GetGlobalVMExclusion, this is the rule to start with:

GetGlobalVMExclusion Allowed

GetGlobalVMExclusion is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "GetGlobalVMExclusion": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every GetGlobalVMExclusion call is checked against it from then on.

FAQ

Questions about GetGlobalVMExclusion

What does the GetGlobalVMExclusion tool do? +

Get a specific global VM exclusion by ID. It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on GetGlobalVMExclusion? +

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

GetGlobalVMExclusion is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit GetGlobalVMExclusion? +

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

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

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

KEEP EXPLORING

More on Veeam VBR v13 MCP Server, and thousands of servers like it.

This server

All 328 Veeam VBR v13 MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →