This week a DevOps engineer asked r/devops a question his team would not hear from him directly: how do you tell colleagues their AI agent should not have root?
His team's setup will sound familiar. The agent "doesn't make mistakes anymore." They built a logging harness around it, so everything is recorded. And whenever it needs to look at a server, it gets root — to all of production. Read-only would do. Root is just easier.
Here is the problem nobody in that thread could argue away.
A log the writer can edit is not evidence
Logging is detection. It is not prevention. And with root, the thing you are logging can edit the harness, the logs and the backups. If the agent ever goes wrong — a bad command, a poisoned instruction, a silent model update that changes its behaviour — the first thing it can touch is the record of what it did.
Your audit trail is only an audit trail if the audited cannot rewrite it.
Root also widens what "wrong" can reach. The agent reads tickets, web pages and log lines to do its job — any of them can carry an instruction it was never given by you. With root, that instruction runs as root. And everything the agent reads — .env files, keys, customer data — can end up sent to a third-party model provider. That is not a hypothetical. That is the design, working exactly as built.
"It hasn't made a mistake in months" is not a control. The model under your agent can change without your team changing anything.
The guardrails that actually hold
Read-only by default. The agent looks with read access. Looking is most of the job.
Scoped, short-lived credentials. One system, one task, one expiry — never a standing master key.
Approval for writes. A human says yes before anything changes. The agent proposes; it does not apply.
Staging first. New playbooks earn production. Nothing debuts at 3AM on the real thing.
The agent never touches its own leash. Logs and backups live where the agent's credentials cannot reach, with a copy it cannot edit.
Treat everything it reads as untrusted. Tickets, pages and logs are input, not orders.
None of this slows a good team down for long. All of it survives the night the agent — or the thing whispering to it — stops being careful.
My agents work the 3AM shift so no human has to. They work it fenced, watched by logs they cannot rewrite, holding keys that expire before the coffee does.
If your agent went wrong tonight, would your logs tell you the truth — or its version of it?
Disclaimer
This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.
I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.
Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.
Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.
Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.
© 2026 Honey Kiran. All rights reserved.
Honey Kiran · DevOps & Platform Engineering
AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.
Examples are illustrative — validate in your own environment before running in production.

Top comments (0)