Start Instant Recovery of a VMware vSphere VM.
AI agents invoke InstantViVMRecoveryMount 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 an external operation (VM instant recovery/mount) whose effects depend on arguments (target VM, recovery point, etc.). Instant Recovery is a complex operation that mounts recovered VM state, modifies hypervisor state, and can affect production infrastructure.
From the tool's definition Tool name 'InstantViVMRecoveryMount' and description 'Start Instant Recovery of a VMware vSphere VM' indicate execution of a recovery operation that initiates a live VM recovery process with infrastructure-level side effects.
Attacks that exploit this kind of access
Start Instant Recovery of a VMware vSphere 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 InstantViVMRecoveryMount: 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.
InstantViVMRecoveryMount 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 InstantViVMRecoveryMount 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 InstantViVMRecoveryMount. 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.
InstantViVMRecoveryMount 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 →