# Can You Undo It? Reversibility Classes for AI Agent Actions

> Source: <https://arxiv.org/abs/2611.22075>
> Published: 2026-11-18 05:00:00+00:00

**Recommendation:** Declare reversibility levels with argument-sensitive rules and capture prior state before tool calls; the session guard gated all 29 attack-positive runs but added nine approvals across 1,209 benign runs.
More in the playbook "Securing agents and AI tools": <https://wpnews.pro/playbooks/agent-security>

arXiv:2611.22075v1 Announce Type: new 
Abstract: Tool-using AI agents change files, databases, access rights and public information, yet permission to call a tool does not establish whether a mistake can be undone. We present Reversibility Classes, a declared five-level vocabulary with argument-sensitive rules, conservative defaults and an explicit prior-state capture contract. The pinned implementation and evidence-linked registry cover 536 tools across 20 MCP servers. All 738 rule-case checks conform to declared expectations, while native annotation mapping differs from draft registry labels for 118 of 481 comparable tools. One AI-assisted reviewer approves 148 ratings, 75 matching the registry; this is not independent agreement. On 2,158 recorded runs, the implemented session guard gates the associated action in all 29 attributable attack-positive runs, compared with 18 for a read/write proxy, while adding nine approval points across 1,209 benign runs. Controlled file, Git, SQLite and three-browser experiments show that recovery depends on captured state, later changes, editor storage and recovery route, and expose a Git merge-state exception. The evidence supports making recovery assumptions explicit and testable. It does not establish registry-wide accuracy, reduced production harm or general recovery reliability.
