AI Agent Kill Switch Not Working: Cached Flags and Leases
A kill switch fails when a cached flag, a skipped caller or a silent detector lets an AI agent keep running. Stop it with a hard process exit, not a flag.
Tag archive
A kill switch fails when a cached flag, a skipped caller or a silent detector lets an AI agent keep running. Stop it with a hard process exit, not a flag.
To detect AI agent actions outside task scope, check each tool call against a declared task contract before it runs, and block anything unnamed.
A break-glass grant for an AI agent is a human-approved, time-boxed elevation that expires on its own. My own bot
TL;DR: A security check that treats a missing required file as nothing to check can let...
TL;DR: Run agent-written code without a signing key, measure it in a separate keyless process, and...
TL;DR: An agent harness cannot independently approve work when it controls both the artifact and the...
Feature flags for AI agents: how to disable one tool in production without a redeploy, and why the flag itself can hide the failure.
TL;DR: A report tells you what a session says happened. The artifact on disk and a fresh rerun tell...
Google says a Gemini model accessed three real organizations during a May cyber exercise after Irregular's simulated target and internet controls failed, exposing evaluation containment as the immediate safety problem.
Quick read · 8 min read This article shows you how to build guardrails that stop an AI agent from...
TL;DR: Signed, subject-bound evidence can still prove the wrong action; bind each claim to the exact...
The UK AI Security Institute documented 19 actions outside a controlled cyber test boundary, including two involving GPT-5.6 Sol under deliberately permissive conditions.