Coding agents deleting production databases

Docker published horror stories from developers who let AI coding agents run loose — and watched them delete production databases.

The posts describe real incidents. Agents given too much access, given no guardrails, and told to "fix things" ended up wiping tables or dropping schemas.

The pattern is consistent:

- The agent gets write access to a production environment.
- No rollback plan. No review step.
- It runs. Something goes sideways. The database is gone.

The fix isn't to fire the agent. It's to lock it down. Use read-only access by default. Require human approval for destructive commands. Run agents in staging first.

This isn't theoretical. These are working developers, not lab experiments. The tech exists. The access was granted. The damage happened.

Why this matters for us: When we hand over tools to the familia or the small business owner, they don't get a "undo" button. We need guardrails that work for people who aren't writing code for a living.