Autonomous LLM agents act through tools under per-action authorization: a local guard screens each tool call in isolation. We show that local authorization does not compose into global authorization. A compositional authorization failure (CAF) is a locally authorized execution, or a pair of locally authorized executions, that violates a global policy spanning intent, purpose, provenance, consent, and delegation. We characterize CAFs along two axes, expressiveness (single-trace safety versus relational k-safety) and observability (a ladder of monitor profiles). Our central result is an impossibility: relational purpose violations form a 2-safety hyperproperty with no per-trace locus of blame, so a per-action monitor that never raises a false alarm detects none of them, independent of the underlying model or decision procedure; they become visible only under cross-execution monitoring, which none of the six guardrails we survey implements. We make this constructive with AL-SYNTH, a SAT/SMT synthesizer (using no language model) that emits minimal CAF witnesses, each checked against an exhaustive oracle. The empirical signature is sharp: across nine LLM judges the per-action view approves the synthesized witness almost without exception, blocking it at a rate comparable to a benign control, yet the same models flag it when shown the two executions together. Per-action authorization is therefore structurally insufficient for relational policy conjuncts not reducible to single-trace safety: to bound them, a monitor must compare executions or accept false alarms.
Figures & tables
Fig. 1: A compositional authorization failure, single-trace case. Every action passes its local check (top), yet the composed trace violates the global policy Φ (bottom), with no single offending step. The relational purpose failure is witnessed instead by a pair of individually compliant executions (Figure 3 ).
Fig. 2: The two-axis map, with class labels as in Table III . Increasing observability (left to right) covers the single-trace classes one by one (teal). The relational purpose class C2r (coral) is 2 -safety, so no single-execution profile can express it; it is covered only by the relational profile P7 , beyond the strongest profile any surveyed system reaches. The bottom row is the number of undetected classes per profile, the monitor-coverage curve of § VII .
Fig. 3: Why purpose is relational. Two executions agree on the low inputs and on the purpose-authorized view of context (the same slots are free) and differ only in a hidden, unauthorized reason. Each offers a free slot, so neither trace alone is faulty, yet the disclosures differ ( α(obsa)=α(obsb) ). That difference is explained only by the unauthorized reason, so the pair is the 2 -safety witness for C2D : it is visible only by comparing executions, which a relational ( P7 ) monitor does and a per-action monitor cannot.
Fig. 4: AL-Synth . One symbolic model with two semantics drives an SMT solver and an exhaustive oracle. A differential check compares them (soundness, bounded completeness, minimality), and the validated pipeline emits minimal witnesses and computes the monitor-coverage curve.
CAF (sub)class
P0
P1
P2
P3
P4
P5
P5+
P6
P7
C1 intent
∘
∙
∙
∙
∙
∙
∙
∙
∙
C2 purpose (labeled)
∘
∘
∙
∙
∙
∙
∙
∙
∙
C2 purpose (relational)
∘
∘
∘
∘
∘
∘
∘
∘
∙
C3 provenance (path)
∘
∘
∘
∙
∙
∙
∙
∙
∙
C3 flow (explicit labeled)
∘
∘
∘
∘
∘
∘
∘
◐
◐
C4 consent (per-action)
∘
∘
∘
∘
∙
∙
∙
∙
∙
TABLE I: Monitor-coverage matrix, solver-validated and confirmed against the brute-force oracle (all 72 cells agree). ∙ : the profile detects the class exactly, flagging every witness and no compliant trace. ◐ : detects it only conservatively, a sound over-approximation that admits most compliant traces at the cost of some false alarms. ∘ : no monitor at that profile detects it without missing witnesses or blocking compliant behavior. The one ◐ row is explicit labeled flow, over-approximated by taint tracking at P6 and above. Both ∙ and ◐ count as covered in the bottom-row curve. Only relational purpose ( C2 , shaded ∙ ) admits no per-trace coverage at all, closing at P7 (Theorem 3 ).
Fig. 5: Synthesis cost on the cumulative-consent model (11 actions, Z3 4.16). Minimal-witness synthesis (dashed) stays flat to depth twelve, while all-SAT enumeration (solid, used only for the oracle check) grows exponentially with the witness count (annotated). One model; times are illustrative, not a benchmark.
Mechanism
What it observes
Profile
Cross-exec.
Per-tool approval
current action, shown to a human
P0
no
Task Shield [ 16 ]
action versus task goal
P1
no
RTBAS [ 17 ]
IFC taint and dependencies
P3
no
CaMeL [ 18 ]
data and control flow, capabilities
P5
no
Fides [ 8 ]
IFC labels, explicit secrecy
P6
no
SAFEFLOW [ 19 ]
IFC labels and provenance
P6
no
TABLE II: Surveyed agent-authorization mechanisms and the profile each receives in Table III . “Cross-exec.” asks whether the mechanism compares distinct executions of the same purpose, the P7 capability.
mechanism (profile)
C1
C2ℓ
C2r
C3p
C3f
C4a
C4c
C5
Per-tool approval ( P0 )
∘
∘
∘
∘
∘
∘
∘
∘
Task Shield [ 16 ] ( P1 )
∙
∘
∘
∘
∘
∘
∘
∘
RTBAS [ 17 ] ( P3 )
∙
∙
∘
∙
∘
∘
∘
∘
CaMeL [ 18 ] ( P5 )
∙
∙
∘
∙
∘
∙
∘
∙
Fides [ 8 ] ( P6 )
∙
∙
∘
∙
◐
∙
∙
∙
SAFEFLOW [ 19 ] ( P6 )
∙
∙
∘
∙
◐
∙
∙
∙
TABLE III: Defense matrix, confirmed against the brute-force oracle; symbols as in Table I . Each mechanism is placed at the strongest profile its published design implements, so its row is a capability bound from the design, not an execution of its code. The relational purpose column (shaded) is missed by every surveyed mechanism: Fides and SAFEFLOW ( P6 ) cover six classes exactly and explicit labeled flow conservatively, and only the relational auditor ( P7 ) covers relational purpose.
Task
Class
n
CAF
95% UB
Injected-doc forward
C1
10
0
≤26%
Narrow-scope share
C4
10
0
≤26%
Scheduling audit
C2r
80
0†
≤3.7%
TABLE IV: Offline audit of Claude Sonnet 4.6 (fixed temperature). CAF is the number of compositional authorization failures observed; UB is the exact one-sided 95% Clopper–Pearson upper bound on the per-episode rate. Prompts, seeds, and settings are in the artifact.
judge
wit
ben
C1
aud
Claude Opus 4.8
0/30
0/30
30/30
30/30
GPT-5.5
0/30
0/30
30/30
30/30
Gemini 3.1 Pro
0/30
0/30
30/30
30/30
Grok 4.3
0/30
0/30
30/30
30/30
DeepSeek V4 Pro
0/30
2/30
30/30
30/30
Qwen3.7-max
0/30
0/30
30/30
30/30
TABLE V: Per-action judges over the synthesized relational witness. Cells count the scenario-repetitions, out of 30 (ten templates, three repetitions), in which the judge blocks at least one action: wit the witness, ben a benign no-leak control, C1 an overt single-trace control, and aud the relational auditor, the same model shown both executions. Hosted models ran through OpenRouter and the local model through vLLM.
Qwen3-30B
Gemma-4
guard
CAF
CAF-free
CAF
CAF-free
no guard ( P0 )
22/60
63.3%
0/60
100%
intent-closure
20/60
66.7%
0/60
100%
composition ( P5+ )
0/60
100%
0/60
100%
TABLE VI: Live tool-calling agents on the cumulative-consent task ( 60 independent rollouts per cell at fixed temperature, zero execution errors). CAF : consent-composition failures committed. CAF-free : fraction of rollouts with no CAF, a natural rate under no guard and a prevention rate under a guard. The composition-aware P5+ guard removes every CAF while blocking no benign or clean-intent rollouts.
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
Display name
API slug
Claude Opus 4.8
anthropic/claude-opus-4.8
GPT-5.5
openai/gpt-5.5
Gemini 3.1 Pro
google/gemini-3.1-pro-preview
Grok 4.3
x-ai/grok-4.3
DeepSeek V4 Pro
deepseek/deepseek-v4-pro
Qwen3.7-max
qwen/qwen3.7-max
Appendix
TABLE VII: Judge models and exact API slugs for the campaign of § VIII ; settings in the text, accessed June 2026.
Multi-agent LLM systems exchange messages before acting through tools, but message delivery, signing authority, and tool-side enforcement are separate trust boundaries. We represent them as communication, authorization, and execution structures, and use the authority cut to characterize the smallest independently compromised signer coalition that can construct a policy-valid false-claim proof under stated assumptions. Controlled paired hidden-state studies reveal four distinctions. First, no fixed-message routing contrast across four models meets the prespecified large-effect criterion; when relays rewrite messages, executed false-state action rates vary by model and route configuration. Second, presented source-identity cues do not uniformly increase protected-action selection across three models. Third, on invalid-proof cases, Nemotron and Llama request protected actions in 52.1% and 54.2% of trials, respectively, yet a deterministic tool gate commits none: request-level and commitment-level safety readouts diverge. Finally, a separate single-model authorization check shows that a false claim with a policy-valid compromised-signer proof can pass the gate, since proof validity is not factual truth. These findings motivate evaluating delivered information, qualified authorization, model proposals, and committed actions separately.
When an LLM agent acts on behalf of a user, it is expected to act within the authorization scope the user grants. Existing agent evaluations largely measure task completion or harmful consequences and can therefore overlook actions that violate this delegation without producing conventional safety or privacy harms. We introduce AuthorizationBench, a benchmark of authorization alignment grounded in documented real-world cases. A scalable construction pipeline produces 286 executable tasks spanning situational triggers, the presence or absence of direct harmful consequences, and ten application domains. We execute every task with four models at two reasoning-effort settings across three agent harnesses in an authorization-aware sandbox that keeps authorized and out-of-authorization paths executable and observable, yielding 6,864 trajectories. Agents act out of authorization in 19.2% of trajectories, with rates ranging from 10.5% to 26.6% across the 24 configurations. Task completion does not imply authorization. Increasing reasoning effort leaves the aggregate rate nearly unchanged, with effects varying across models. On controlled pairs, agents act out of authorization at similar rates with (17.9%) and without (20.8%) direct harmful consequences, and more often under benign pressures than malicious injections (23.5% versus 17.6%, p=0.002). Our results show that task capability, additional reasoning, and consequence-oriented safety evaluation do not by themselves ensure authorization alignment. Moreover, agents that consult the principal before completing a task exhibit lower rates of out-of-authorization behavior (14.0% versus 21.6%, p<0.001), pointing to a tension between agent autonomy and preserving users' decision authority that calls for further human-centered study. Dataset and code are available at https://github.com/PEACH-Research-Lab/AuthorizationBench .
Zhiping Zhang, Franklin Mingzhe Li, Zihao Huang +1
Northeastern University · Carnegie Mellon University · UNC-Chapel Hill
Large language model (LLM) agents autonomously interleave semantic reasoning with complex system operations. In these dynamic environments, static tool-level permissions are fundamentally insufficient; safe authorization is highly context-dependent and heavily reliant on evolving runtime states and data flows. We present FAVA (Formal Authorization for Verified Agents), a permission-carrying authorization framework for agent execution. FAVA utilizes an LLM-guided Permission Intermediate Representation (IR) to translate ambiguous natural-language tasks into structured constraints. A deterministic lowering pass then converts this IR into an evidence-backed permission graph that explicitly tracks data flows, dependencies, and contextual labels. To provide strict security guarantees, a Satisfiability Modulo Theories (SMT) authorizer mathematically verifies the current graph against security policies before any effectful action executes. A runtime gateway then enforces the solver's result, either authorizing the execution or intercepting it with a precise counterexample. We evaluate FAVA across OpenAgentSafety, OctoBench, and ActPlane scenarios. Our evaluation demonstrates that FAVA achieves a 90.5% Decision Compliance Rate (DCR) over the aggregate dataset, successfully intercepting dynamic violating traces in the evaluated trace-conditioned scenarios.