{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidvvteszxtpyepus6ee67dtlr4vl64ow2o2twa2w73kvjudgifes4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mpdycst7uw42"
  },
  "path": "/t/whats-the-worst-thing-your-ai-agent-did-in-production-without-asking-first/1384608#post_2",
  "publishedAt": "2026-06-28T11:45:36.000Z",
  "site": "https://community.openai.com",
  "textContent": "The failure I watch for is a write action that looks reasonable but was based on stale context. It is less dramatic than “agent deleted everything”, but it is the kind of mistake that slips past demos.\n\nThe guardrail I would add afterward is to split tools by action class: read, draft, modify, delete, spend. For modify/delete/spend, make the first call produce a dry-run receipt: exact target id, proposed before/after diff, external system touched, and why the agent thinks it is allowed. Only a separate approval step can run the real action.\n\nAlso log the denied path. If the agent keeps trying the same blocked action after a human says no, that is a loop/control bug, not just a prompting issue.",
  "title": "What's the worst thing your AI agent did in production without asking first?"
}