This is an expected behavior and is by design. This is because an individual ESX/ESXi host cannot confirm the current state of vCenter Server and, in general, the state of the vSphere Distributed Switch.
Such modifications are only allowed from the vSphere Client or the vSphere Web Client connected to vCenter Server.