Letting AI agents touch production infrastructure without a control layer sitting underneath is the kind of decision that looks reasonable in a demo and catastrophic six months later. CloudBolt‘s latest update to its cloud management platform addresses that tension directly, adding support for the Model Context Protocol while expanding the governance tools enterprises need before they can responsibly hand any operational task to an AI assistant.
The MCP integration changes how AI tools interact with CloudBolt CMP in a meaningful way. Rather than giving an AI agent open access to infrastructure functions, the protocol allows approved agents and conversational interfaces to communicate with the platform through a standardized channel while the platform itself stays in control of what actually happens. Permission checks, policy enforcement, and audit trails all remain active underneath. An AI assistant can request provisioning, surface available actions based on a user’s role, or trigger approved post-deployment tasks, but none of that bypasses the governance layer that enterprise operations teams depend on to stay compliant and accountable.
That distinction matters more than it might seem. As organizations experiment with AI in infrastructure workflows, the question shifting to the front of every serious conversation is not whether automation is technically possible but who controls what the automation is allowed to do. CloudBolt COO Yasmin Rajabi framed the release around exactly that concern, noting that enterprises need a way to connect AI-assisted workflows to their infrastructure without creating a new governance problem in the process.
Beyond the MCP addition, the update also tightens how permissions flow within infrastructure teams. Many organizations currently grant broad administrative access when someone needs to perform a narrow task, simply because the platform does not offer a cleaner alternative. The revised access controls let administrators expose specific actions to specific users without extending wider rights, which makes internal self-service models considerably safer to run at scale.
The release furthermore extends structured workflows into day-two operations, covering the resizing, updating, remediating, and decommissioning tasks that follow initial provisioning and have historically required manual specialist effort.
Additionally, CloudBolt continues expanding its support for VMware alternatives, adding integrations across OpenShift Virtualization, Oracle Linux Virtualization Manager, and Hyper-V, with SUSE Virtualization and neocloud environments including CoreWeave and Vultr coming next.
For enterprises managing increasingly fragmented infrastructure across public cloud, private cloud, and alternative virtualization stacks, that breadth of coverage addresses a real and growing operational headache.
