---
title: "Comment by Evelyn Wyatt on \"How Should Accountability Be Assigned When AI Agents Make Wrong Decisions?\" | Hashnode"
description: "The point about “permission creep” is especially important. An agent may be properly scoped when it is first deployed, but once new tools, data sources, and wor"
url: "https://hashnode.com/posts/how-should-accountability-be-assigned-when-ai-agents-make-wrong-decisions/6a969f1c187d2f11ab840320/comment/6a96c8e584c37c94a23d937d"
---

[Discussion](https://hashnode.com/posts/how-should-accountability-be-assigned-when-ai-agents-make-wrong-decisions/6a969f1c187d2f11ab840320)

Comment [How Should Accountability Be Assigned When AI Agents Make Wrong Decisions?](https://hashnode.com/posts/how-should-accountability-be-assigned-when-ai-agents-make-wrong-decisions/6a969f1c187d2f11ab840320)

[Evelyn Wyatt](https://hashnode.com/@Evelynwyatt)

[Sep 1](https://hashnode.com/posts/how-should-accountability-be-assigned-when-ai-agents-make-wrong-decisions/6a969f1c187d2f11ab840320/comment/6a96c8e584c37c94a23d937d)

The point about “permission creep” is especially important. An agent may be properly scoped when it is first deployed, but once new tools, data sources, and workflows are added, the original accountability model can become outdated. I think periodic permission reviews should be treated almost like security reviews, especially for agents that can take irreversible actions.
