Share your thoughts, 1 month free Claude Pro on usSee more
WorkDL logo mark

Context-to-Execution Integrity for LLM Agents

About

Language-model agents read attacker-writable context to solve tasks. Tool execution needs a separate authority check for protected sink fields, sink-interpreted payloads, and the invocation event. Context-to-Execution Integrity (CXI) is an execution-boundary system for this setting. Policies mark protected sink fields, typed releases carry narrow validated values from writable context to specific destinations, opaque data slots keep evidence as data, and a deterministic gate admits a call only after field authority, exact-effect authorization, and invocation authority all bind to the same action manifest. We evaluate CXI on open-weight field-projection runs, AgentDojo live episodes, a code-agent exact-effect benchmark, manifest-bound ledger faults, proposal-pressure controls, and hosted/API compatibility traces. AgentDojo covers 720 live episodes and 1,739 LLM calls; the code-agent benchmark covers 400 repository episodes with exact-effect authorization and lease-bound execution, yielding 231 safe task completions and zero observed field, effect, or invocation escapes. The accounting reports parser outcomes, authorization outcomes, and task-quality outcomes together with the admission-integrity result. Across the evaluated sinks, CXI admits execution only when field, effect, and invocation authority bind to the same action manifest.

Igor Santos-Grueiro• 2026

Related benchmarks

TaskDatasetResultRank
Admission IntegrityAgentDojo exact-effect admissions
Field Records306
1
Agent Task Utility and Admission IntegrityAgentDojo (live task bank)
STC199
1
Agent Task Utility and Admission IntegrityCode-agent exact-effect benchmark
STC Count231
1
Field-local Selection CompatibilityHosted API field-local (compatibility)
Unsafe Selections Blocked85
1
Ledger Integrity and Admission ControlManifest-bound ledger (faults)
Rejects19
1
Showing 5 of 5 rows

Other info

Follow for update