CrowdStrike announced an AI kill switch for Falcon Guardian on November 3, 2026, saying it was available that day. For security teams and business owners deploying AI agents—software that uses tools to carry out tasks—the practical question is which parts of a workflow it can stop.
Its current intervention blocks model access through connected gateways. A gateway is an intermediary through which an application reaches an AI model. The practical distinction: interrupting that access is not the same as terminating the running software or cancelling work already sent elsewhere.
What is available now
According to CrowdStrike’s launch details, Guardian directs Falcon AI Gateway or connected third-party gateways to block model access. Existing infrastructure must support that connection; the announcement is not a compatibility guarantee for every gateway.
Falcon AI Gateway is generally available. CrowdStrike says it is included with Guardian at no additional cost. That is a bundling term, not a free standalone service or a promise that model usage is free.
The product page describes blocking designated models and providers. Targeting by agent type is still planned, so buyers should not assume they can isolate any individual agent with today’s switch.
Coordinated process termination, restart prevention and permission revocation, along with wider cloud, business-application and browser containment, are future extensions. Those plans do not establish current integrated coverage or delivery dates; they are distinct from any separate response controls a business already uses.
Check the route, then the work already underway
Map each workflow’s normal and backup model connections. The following is an analysis of CrowdStrike’s documented gateway boundary, not a report of tested behavior:
Connected gateway. Confirm that the selected model route and your configured blocking scope are supported. Existing Falcon software on a device is not, by itself, evidence that its model traffic passes through that gateway.
Direct, local or backup route. Do not count a model connection outside the gateway as covered by this cutoff. A locally hosted model is not automatically excluded if its requests pass through a supported connected gateway; routing is what matters.
Work already dispatched. Identify who can cancel jobs in business applications and suspend the agent’s separate access. Blocking another model request does not establish that a queued task is cancelled or a completed change reversed.
Shared model or provider. Identify legitimate workflows within the same blocking scope. They may also be interrupted. Confirm the exact isolation available rather than assuming either a company-wide stop or individual-agent targeting.
For teams building their own Claude-based agents, the related guide to blocking actions when custom checks fail covers a separate application-level control. It should not be confused with Guardian’s model-access cutoff.
What to confirm before relying on it
Ask CrowdStrike or your provider to confirm compatible gateways and versions, your entitlement, and the accounts and sessions affected. The public launch material does not settle handling of requests already in progress or supply a measured end-to-end stopping time.
Get a quote separating Guardian, any third-party gateway, model consumption and integration work. The cited Guardian product page does not provide a numerical subscription price.
Agree who can activate the cutoff, who can restore access and how queued work will be reviewed before restart. CrowdStrike says an authorized administrator triggers the action and that actions are audited.
The decision: use the current switch as a model-access control where the route is covered. Keep separate controls for running software, business-tool access and outstanding work; do not base an emergency-stop plan on integrations that have yet to ship.