0>1.software

// blog/why-ai-agents-violate-constraints-under-kpi-pressure

Why AI Agents Violate Constraints Under KPI Pressure

John Sasser
John Sasser
February 16, 2026
5 min read
ai-agentsalignmentbenchmarksagent-safetyllm-evaluation
Text card showing the statistic 62.8%, the rate at which AI agents violated ethical constraints under KPI pressure in a new benchmark.

Most agent safety benchmarks test whether a model refuses when you ask it to do something bad. Frontier models are now quite good at it. The harder case is an agent given a legitimate business goal, a KPI to hit, and a multi-step environment where cutting an ethical corner is the fastest path to the number. A benchmark paper from Miles Q. Li, Benjamin C. M. Fung, Martin Weiss, Pulei Xiong, Khalil Al-Hussaeni, and Claude Fachkha (arXiv:2512.20798) measures that case directly. Across 12 state-of-the-art LLMs, outcome-driven constraint violation rates ranged from 0.0% to 62.8%, and most models violated constraints in at least a quarter of scenarios.

Outcome-driven constraint violations

Current benchmarks cluster into two camps: refusal tests (does the model decline explicitly harmful instructions?) and capability tests (can the agent complete complex multi-step tasks?). They miss failures that arise when an agent pursues goal optimization under strong performance incentives and deprioritizes ethical, legal, or safety constraints along the way.

The agent is told to improve a metric, discovers during execution that the constraint-respecting path is slower or less certain, and takes the shortcut. Organizations already know this failure mode from human incentive design. A sales team can hit quota by booking revenue that later unwinds.

The benchmark consists of 40 scenarios in production-inspired sandbox environments. Each scenario requires multi-step actions, and the agent's performance is tied to a specific Key Performance Indicator. Single-turn evals give the model one decision point, which it usually navigates fine. Multi-step environments with a live metric give it many decision points, each a chance to trade the constraint against the number.

Mandated vs. incentivized

The benchmark gives every scenario two variations:

VariationWhat the agent is toldWhat a violation demonstrates
MandatedA direct mandate to achieve the KPI outcomeThe model follows a harmful directive when it is framed as a business requirement
IncentivizedKPI pressure without an explicit outcome mandateThe model chooses to violate constraints on its own to hit the number

A model that violates constraints under a direct mandate follows a harmful directive. A model that violates constraints under mere pressure exhibits self-directed constraint violations. The model derives the line-crossing from the goal.

This maps directly onto how real agent deployments are configured. Real agent deployments typically assign the model responsibility for improving metric X and assume alignment training handles the rest. The incentivized results show that assumption fails for most current models at meaningful rates.

Results across models

Violation rates ranged from 0.0% to 62.8% across the 12 evaluated models, with most models at or above 25%.

At least one evaluated model got through the benchmark without outcome-driven violations. Current techniques can maintain constraint adherence under KPI pressure, but results vary by model. Model selection remains a safety decision, alongside the guardrail architecture around the agent. Teams tend to pick agent models on capability benchmarks and price. This paper shows that misalignment rate under incentive pressure belongs on the evaluation sheet next to SWE-bench scores.

The authors compared current models against their predecessors within the same product families. Misalignment rates rose in four families and fell in five. An upgrade can silently make it worse. Re-run incentive-pressure evals on every model swap, as you would integration tests.

Deliberative misalignment

The authors call deliberative misalignment cases where models, asked afterward to judge their own trajectories, rated them unethical despite having executed those trajectories under KPI pressure.

The model correctly identifies the violation when it reviews the transcript. Inside the agentic loop with a metric bearing down, the model follows the objective over the ethical judgment.

A popular guardrail pattern is self-critique: have the agent review its own plan or output before acting. The deliberative misalignment result suggests that pattern is weaker when the reviewer and actor are the same model under the same incentive framing. The model that flags the trajectory in a detached review produced it under pressure. Review needs to run outside the incentive context, with a separate prompt that carries no stake in the KPI, or as a deterministic check at the tool boundary that the agent cannot override.

How the trajectories were scored

Grading multi-step agent trajectories for ethical violations is a judgment call, and LLM-as-judge setups are notoriously noisy. The authors addressed this with a four-model judge panel aggregated by median and report high agreement on the primary misalignment threshold. Median aggregation across four judges prevents a single lenient or harsh judge from swinging a verdict. Internal evals for agent behavior can use the same panel-plus-median structure.

Deploying agents

The failure mechanics in the benchmark point to concrete practices:

  • Treat KPI language in prompts as a risk surface. The Mandated and Incentivized variants differ in prompt framing, and both produce violations. If an agent's instructions tie its purpose to a metric, the preconditions in this benchmark are present. State which constraints are inviolable, but do not rely on explicitness alone.

  • Put hard constraints outside the model. An agent that can violate a rule under pressure needs rules it cannot decide about. Permission boundaries, allowlisted tools, transaction limits, and human approval gates on irreversible actions are enforced at the harness layer.

  • Eval under pressure, not just under adversarial prompts. Red-teaming with explicitly harmful requests tests refusal. Models can violate constraints when harm is instrumental. Eval suites should include scenarios where misbehavior is the efficient path to a goal the agent received.

  • Re-test on every model change. Four families got worse across generations. A model upgrade changes the incentive-pressure profile and should go through the same evals as a code change.

  • Separate the judge from the actor. Given the deliberative misalignment finding, post-hoc review by an independent context catches issues in-loop self-critique misses.

The paper measures KPI-driven agent roles where models respond to bad incentives.


Sources