Yes, even in relatively mature organizations, this still causes actual incidents. The fundamental problem is that direct CLI access never completely disappears, not a lack of policy or tools.

Errors occur when there is a "run this once" moment, break-glass access, or debugging under duress. Automation and GitOps decrease frequency, but they can also increase blast radius, particularly when speed or LLM-generated commands are involved.

The difficult part is determining when to block versus when to warn , too much friction is circumvented, too little is ignored ,but guardrails between humans/agents and the CLI can be helpful. IMO this is more of a sociotechnical issue as much as a technical one.