Capability-Gated Language Models: Security Composes, Utility Does Not

Patrikas Vanagas, Augustas Mačijauskas, Laurynas Lopata
8/31/2026
cs.CRcs.AIcs.LG

No official code found. Best implementation: patrikasvanagas/capability-gated-deployment (0 stars, MIT, last commit 2026-10-05).

Abstract

Deployed language model safeguards (safety fine-tuning, filtering, unlearning) vary by principal only outside the model weights: filters are reconfigured, tiers are multiplied, and artefacts are reissued; inside one set of weights every request meets the same model configuration. This motivates us to define capability-gated deployment: per-principal access control inside one set of weights, whose configurations form a lattice - meets accumulate a principal's restrictions and joins pool a coalition's reach. We instantiate it by sparse rank gating over an existing nested-factorisation mechanism, guide profile search with one-pass attribution, and read every result once from a pre-registered held-out split. Security composes: provably at meets under a monotone-elicitation assumption we falsify pointwise. In two lineages the median held-out meet deepens suppression; the one effect surviving correction strengthens it. Utility does not: individually harmless profiles can compose to retention and fluency damage, and no compositional bound exists.

View on arXivView PDF

Code Implementations(1)

MIT

Capability-Gated Language Models: Security Composes, Utility Does Not (NeurIPS 2026 FLMSec)

00Python, Jupyter NotebookOct 5, 20262 weeks agoMIT

Similar Papers

Cite this paper

@article{vanagas2026capabilitygated,
  title  = {Capability-Gated Language Models: Security Composes, Utility Does Not},
  author = {Patrikas Vanagas and Augustas Mačijauskas and Laurynas Lopata},
  year   = {2026},
  eprint = {2609.00445},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2609.00445v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2609.00445.svg)](https://codeofpaper.com/paper/2609.00445)

Discussion