- A cost kill switch for GenAI: stopping runaway token spend automatically on Azure and AWSAI & GenAI · 25 Oct 2026
- A feature-level kill switch for LLM features with Azure App Configuration feature flagsAI & GenAI · 25 Oct 2026
- A gateway kill switch for all LLM traffic: Azure API Management named values and policiesAI & GenAI · 25 Oct 2026
- AI kill switches explained: the six levels you can switch off and how to design each oneAI & GenAI · 25 Oct 2026
- Automated tripwires: signals that should pull a GenAI kill switch without waiting for a humanAI & GenAI · 25 Oct 2026
- Blocking one abusive user or tenant from your GenAI service without taking it down for everyoneAI & GenAI · 25 Oct 2026
- Checklist: testing AI kill switches with regular drills before you need themAI & GenAI · 25 Oct 2026
- Emergency cut-off for a model endpoint: blocking all access to Azure OpenAI or Bedrock in minutesAI & GenAI · 25 Oct 2026
- Kill switches for self-hosted models on Kubernetes: ingress, network policy, scale to zeroAI & GenAI · 25 Oct 2026
- Safe mode for a GenAI assistant: what to switch to when the model's answers can't be trustedAI & GenAI · 25 Oct 2026
- Sev1: an AI agent is taking harmful actions. The emergency stop runbookAI & GenAI · 25 Oct 2026
- Sev1: the RAG assistant is showing documents people shouldn't see. Pulling the data sourceAI & GenAI · 25 Oct 2026
- Switching off one agent tool without stopping the agent: tool-level kill switches and MCP serversAI & GenAI · 25 Oct 2026
- The rollback switch: returning to the last good model or prompt version in one stepAI & GenAI · 25 Oct 2026
- Who may pull the AI kill switch? Roles, decision rules, communication and audit trailAI & GenAI · 25 Oct 2026