Enable maintenance mode on a SOBR extent.
AI agents invoke EnableScaleOutExtentMaintenanceMode 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.
Enabling maintenance mode on a Scale-Out Backup Repository (SOBR) extent triggers an external operational state change on backup infrastructure. This is not a simple data read or write — it actively changes the operational mode of a storage extent, potentially causing Veeam to evacuate data, stop using that extent, and affect ongoing backup/restore jobs.
From the tool's definition Enable maintenance mode on a SOBR extent
Attacks that exploit this kind of access
Enable maintenance mode on a SOBR extent. 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 EnableScaleOutExtentMaintenanceMode: 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.
EnableScaleOutExtentMaintenanceMode 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 EnableScaleOutExtentMaintenanceMode 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 EnableScaleOutExtentMaintenanceMode. 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.
EnableScaleOutExtentMaintenanceMode 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 →