
Read-Only Debugging Agents for Production: A Capability Envelope You Can Audit (2026)
An agent that can look at a production incident is useful. An agent that can also change production is a second incident waiting for a bad day. Most teams resolve that tension by choosing one extreme: hand the agent the same credentials an on-call engineer uses, or keep it out of the incident entirely and go back to kubectl and grep. The direct answer to the middle path is this: “read-only” is not one control, it is four, and they do not fail together. The agent’s tool selection is advisory. The other three — the credential or API scope the call travels over, the database transaction mode, and the runtime guard on evaluated expressions — are enforced somewhere outside the agent’s goodwill. A session is only as safe as the outermost enforced layer, and it is only auditable if the enforcement decision is recorded per call. ...