Menu

How do I make colleagues aware of the risks of giving an LLM agent root access to production?

#devops#redditdevops#agent#access#root
Reading 0:00
15s threshold

I could use some advice on a situation at work.

A few colleagues in ops have, almost overnight, started to fully trust their LLM agent because it has gotten so good lately and "doesn't make mistakes anymore". They built their own harness around it and log what it does (using Grok and Google models), but the agent still runs with root access to our entire production infrastructure. We have no clear team rules or policy yet, and they don't see the danger themselves.

A typical example: whenever the agent needs to check something on a server, they just hand it full access. But looking at info only needs read-only access. The permission should match the task, not the most convenient option.

My concerns:

Logging is detection, not prevention. It shows what broke afterwards, but doesn't stop anything.

Root bypasses the harness. An agent with root can in theory edit the harness, the logs and the backups, so those logs are not a reliable audit trail.

No least privilege.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.