Technical report / Version 2
What Does an AI Kill Switch Prove? Evidence and limits of shutdown at an agent tool gateway
OPAQUE Systems
Abstract
A shutdown command, a signed refusal and the absence of subsequent effects are different observations. We examine those distinctions using the merged cMCP gateway kill switch and its accompanying policy-key and delegation revocation mechanisms. A reproducible evaluator drives gateway startup, signed agent identity, Cedar evaluation, loopback HTTP tool calls, durable blocks, process restart, recovery and offline receipt verification. The reference run satisfies 27 named assertions. Two targeted implementation weakenings are detected at their intended assertions. Separately, 81 existing cMCP component tests and 38 cA2A revocation tests pass on pinned source revisions. The observed system refuses new tool work through the stopped gateway and retains its block after restart. An admitted call can nevertheless finish during shutdown, a direct tool path can produce an effect while the gateway is stopped, and a historical refusal still verifies after recovery. These counterexamples establish the limits of treating a signed receipt as evidence of continuing or universal shutdown. An external evaluator repeated the reference run, both weakenings and both component suites on his own workstation and obtained the same outcome for every assertion. We propose an evaluator protocol that separates admission, effects, persistence, recovery and freshness, with an explicit role for independent observation. The exercise uses software keys, one operator and no model or confidential hardware.
What this report contributes
An evaluator protocol that separates admission, drain, persistence, recovery and evidence at a tool gateway, with counterexamples to reading a signed refusal as proof of continuing shutdown.
Evidence and limits
- Software-only, on Windows hosts with software keys over loopback HTTP. The author and one external evaluator each controlled gateway and observer together; no language model, confidential hardware or independently operated peer was used.
- A direct path to the tool produced an effect while the gateway was stopped, which the gateway's records cannot show, and a call admitted before the trip still completed.
- A historical refusal still verifies after recovery: the receipt verifier accepts no challenge or maximum age, so present shutdown state needs a new observation.
The source package preserves the recorded inputs and results. One external evaluator repeated every run on his own workstation on October 11, 2026, with gateway and observer under his one administrator. One individual's evaluation, not a certification or ongoing verification.
Read the current specification and implementation guidance. This report describes an earlier design and evaluation; the current specification governs implementation.
Cite this report
Imran Siddique. What Does an AI Kill Switch Prove? Evidence and limits of shutdown at an agent tool gateway. AgenTrust technical report, version 2, 2026.
Download BibTeX / Download CITATION.cff
@techreport{agentrust2026killswitch,
title = {What Does an AI Kill Switch Prove? Evidence and limits of shutdown at an agent tool gateway},
author = {Imran Siddique},
institution = {AgenTrust},
year = {2026},
type = {Technical report},
note = {Version 2; not peer reviewed},
doi = {10.5281/zenodo.23308975},
url = {https://agentrust-io.com/research/kill-switch/v2/}
}
Version history
Version 2, October 11, 2026: Adds Section 9: an external evaluator, Zoheb Shaik, repeated the reference run, both weakenings and both component suites on his own workstation on October 11, 2026 with the same outcome for every assertion. Rechecks later source against current main. No version 1 result changes.
Version 1, October 1, 2026: First public edition. Evaluates cMCP 9db65b5 and cA2A 540a578; results were repeated on September 27 and October 1, 2026 with the same outcomes, and later source was rechecked against main.
Revises a discussion draft dated September 19, 2026.
File checksums. Published version files are retained; substantive revisions receive a new version.
Questions and corrections
Open an issue in the project repository and identify the report version and section.