Restore an entire Microsoft Hyper-V VM.
AI agents invoke EntireVmRestoreHv 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.
This tool triggers a restore operation on a Hyper-V virtual machine, which is an external operational action that creates or overwrites a VM's state. While it could be considered Write (creating/modifying a VM), the restore process executes infrastructure-level operations — spinning up compute resources, overwriting disk state, and potentially replacing a running VM — making Execute the most appropriate category.
From the tool's definition Restore an entire Microsoft Hyper-V VM
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Restore an entire Microsoft Hyper-V VM. 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.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for EntireVmRestoreHv: 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.
EntireVmRestoreHv is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the EntireVmRestoreHv 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 EntireVmRestoreHv. 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.
EntireVmRestoreHv 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →