Case · DiggingBeagle record

Option labels can make typed AI decision gates fail open

A typed agent gate remained vulnerable to misleading option names and irrelevant log text in laboratory authorization tests. The work distinguishes dangerous fail-open decisions from harmless fail-closed cost. Deterministic checking over parsed policy fields beat the tested models on six bounded rules.

Scope

Controlled finding or reported disclosure as of 2026-10-08; Lab simulation, not real unauthorized action; different from separate punctuation/JSON judge paper.

Assessment profile

Assessment method
Setting
simulation
Exploitation
demonstrated
Evidence
Grade B
Remediation
mitigation available
AI role
AGAINST AI
Basis and provenance

Desk review of scoped canonical Claims, the pinned SRC-2026-CP3-OPTION-CHANNEL-DECISION Source, and the publicly accessible primary disclosure. The classification applies to the documented setting and prerequisites only. Impact remains unbanded because real victim consequences are not established, and no independent reproduction is claimed. Details: The measured option-label failures have not been established in real production MCP or tool-authorization gateways.

Assessed Oct 13, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Policy definition

    An agent gate receives a proposed action alongside language descriptions for allow and block options.

    Boundary: An agent gate receives a proposed action alongside language descriptions for allow and block options.

  2. 02

    Lower-trust label/context

    Attacker-controlled or irrelevant text changes the model's probability assignment without changing the actual authorized rule.

    Boundary: Attacker-controlled or irrelevant text changes the model's probability assignment without changing the actual authorized rule.

  3. 03

    Authorization boundary

    A resulting fail-open decision would permit an otherwise forbidden action if an external deterministic authorization check does not intervene.

    Boundary: A resulting fail-open decision would permit an otherwise forbidden action if an external deterministic authorization check does not intervene.

Timeline

  1. Oct 8, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-CP3-OPTION-CHANNEL-DECISION-1On the evaluated four models that ingest an option label, a misleading permissive label raised fail-open behavior to 93% to 100% while policy definitions stayed unchanged.supported

Basis: reported finding

Link to claim
CLM-CP3-OPTION-CHANNEL-DECISION-2Six irrelevant lines of server log text raised fail-open behavior from 0% to 63% in one tested policy; deterministic checks over parsed policy fields reached 100% on the six bounded policies.supported

Basis: reported finding

Link to claim
CLM-CP3-OPTION-CHANNEL-DECISION-3The authors evaluated seven open-weight decision models and found allow-or-block accuracy of 36% to 72% on selected content screening tasks, illustrating sensitivity to default choice.supported

Basis: reported finding

Link to claim

Implications

Structured model output is not equivalent to deterministic authorization when its labels and context are linguistic inputs. Keep final allow/deny decisions in policy code; use models for prioritization or explanation rather than the last permission gate.

Controls and mitigations

  • Parse enforceable policy fields into typed values and evaluate access rules deterministically.
  • Treat caller-controlled option labels and tool logs as untrusted, not policy authority.
  • Track fail-open separately from fail-closed errors and test label-swaps rather than relying only on aggregate accuracy.

Unknowns and contradictions

  • The measured option-label failures have not been established in real production MCP or tool-authorization gateways.
  • Reliability under varied policies and genuinely unseen attack distributions is unmeasured.

Sources and citation

Material revision history

  1. Oct 13, 2026 · Published version · first publication · revision 137