What it requires. An action that writes, sends, refunds, cancels or deletes, reachable by the planner with no confirmation step and no human in the loop.
Why it matters. To the planner an irreversible action is just another tool. The interesting version of this check is not "no confirmation anywhere" but "no confirmation on the irreversible ones specifically". On the org this was written against, exactly one of twenty-nine actions required confirmation - the record write - while an action that modifies automation metadata and two that send outbound to a third party carried none.
How to fix it. Set confirmation on every action whose effect leaves the org or cannot be undone, and review the default on any action installed by a package.
Source. General agent design practice; probe of a live org, 31 August 2026
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.