InstantRecoveryVmwareFcdMigrateWithSession
Start FCD disk migration.
This record as markdown: /tools/kid-boy-veeam-mcp-13/instantrecoveryvmwarefcdmigratewithsession.md
What InstantRecoveryVmwareFcdMigrateWithSession does on Veeam VBR v13 MCP Server
AI agents invoke InstantRecoveryVmwareFcdMigrateWithSession 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.
Why InstantRecoveryVmwareFcdMigrateWithSession is rated High
This tool initiates a disk migration operation, which is an active execution that moves data between storage locations. It is not a simple read or write — it triggers an external infrastructure operation (VMware FCD migration) with significant side effects on backup/recovery state. If misused, it could migrate disks to wrong targets or disrupt recovery workflows, warranting high severity.
From the tool's definition 'Start FCD disk migration' — triggers an active migration operation of a First Class Disk (FCD) in a VMware instant recovery session
Attacks that exploit this kind of access
The rule that runs InstantRecoveryVmwareFcdMigrateWithSession 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 InstantRecoveryVmwareFcdMigrateWithSession, this is the rule to start with:
InstantRecoveryVmwareFcdMigrateWithSession stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Veeam VBR v13 MCP Server, apply this rule, and every InstantRecoveryVmwareFcdMigrateWithSession call is checked against it from then on.
Questions about InstantRecoveryVmwareFcdMigrateWithSession
Start FCD disk migration. 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 InstantRecoveryVmwareFcdMigrateWithSession: 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.
InstantRecoveryVmwareFcdMigrateWithSession 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 InstantRecoveryVmwareFcdMigrateWithSession 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 InstantRecoveryVmwareFcdMigrateWithSession. 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.
InstantRecoveryVmwareFcdMigrateWithSession 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