Skip to content

Topic

AI Agent Guardrails

Security measures that limit an AI agent's actions, often by monitoring or restricting its tool calls, to prevent harmful or unauthorized behavior.

Current stories

buildOne report1 publisher

Coinbase trained its 9B fraud reviewer on a reward computed from known labels, with no judge model

Coinbase says a Qwen3.5-9B model post-trained for under $100 beat Claude Opus 4.5 on its Onramp fraud benchmark. The figures are Coinbase's on private data; the reusable parts are the label-based reward and the tier-only, block-only harness.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+25
Incentives55
Confidence55
buildOne report1 publisher

Claude's four $400 payments cleared a $500 single-payment cap in Pink's 80-run test

Pink's 80-run test of Claude and Gemini found two Claude runs that split a $1,600 order into four $400 payments under a $500 cap. The coffee template does not ship a velocity cap by default, and Pink scored its own runs.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap−10
Incentives65
Confidence50
securityConfirmed4 publishers

AI agent guardrails belong at the tool call, Coralogix's CEO argues

Coralogix CEO Ariel Assaraf says a misconfigured Gemini test agent entered three real systems before it stopped itself. His fix is a policy check between the agent and its tools, and the model has no power to override it.

Perspective Coverage

4 publishers
Builder
Builder 30%
Operator
Operator 48%
Investor
Investor 22%

Reality

Evidence50
Adoption
Not scored
Hype gap+20
Incentives65
Confidence55
buildOne report1 publisher

sdlc-playbooks enforces coding-agent phase rules with a gate script that aborts on exit code 2

sdlc-playbooks runs a gate script before each of its seven coding-agent phases, and a failed precondition aborts the Claude Code command with exit code 2. The check binds only at that entry point, so direct script calls and other editing paths still need their own controls.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+10
Incentives45
Confidence35
buildOne report1 publisher

Why one team skipped 2,284 of 2,490 possible test runs, already settled by deterministic assertions

agent-tooltrust ran 206 live model calls instead of 2,490 and reports identical coverage, on the argument that the only thing a real LLM adds is proof that each framework adapter can surface all four verdicts.

Publishers:dev.to

Reality

Evidence45
Adoption12
Hype gap+8
Incentives60
Confidence50
buildOne report1 publisher

The 90-second diff still costs 20 minutes of human review

The expensive part of software work has moved from writing code to proving it. An engineer building agent systems puts the deny outside the model where no prompt can reach it, and says plainly which defects his deterministic checks still miss.

Publishers:dev.to

Reality

Evidence36
Adoption14
Hype gap+22
Incentives52
Confidence44
buildOne report1 publisher

A reviewer that opens every cited file found errors in five of seven agent-drafted replies

Rulestack says only one of the five was the kind of error a string matcher could catch, and the first matcher it wrote cleared the draft anyway, because 76 turns up 1,343 times in the ledgers it searched.

Publishers:dev.to

Reality

Evidence52
Adoption15
Hype gap−8
Incentives58
Confidence45
buildOne report1 publisher

Reversibility, blast radius and stakes together sort a legal agent's actions into four grades before controls attach

A dev.to guide scores every action an AI legal agent takes by reversibility, blast radius and stakes, then attaches controls by grade: maker-checker on anything executed or filed, attorney review on all substantive work product.

Publishers:dev.to

Reality

Evidence32
Adoption
Not scored
Hype gap+15
Incentives72
Confidence52
buildOne report1 publisher

A required Pydantic field forces every warehouse cost estimate to name its accuracy tier

The 18-hour-old cost-guard-mcp gets a real byte count out of BigQuery's dry-run planner and only a planner ceiling out of Snowflake's EXPLAIN, so its type system makes an agent see which of the two it got.

Publishers:dev.to

Reality

Evidence55
Adoption8
Hype gap+12
Incentives78
Confidence50
buildOne report1 publisher

One matching prefix aborts all four writes in a Claude Code audit-memo sync

The gate between Claude Code's self-written audit memos and one developer's Obsidian wiki scans only the four files it intends to copy, tests them against two credential prefixes, and exits 2 on the first match.

Publishers:dev.to

Reality

Evidence58
Adoption8
Hype gap+12
Incentives20
Confidence40
securityOne report1 publisher

Tenable says its own agent planned bulk changes across assets the requester could not modify

Tenable's account of the control layer around Hexa AI lists what broke during development, including an agent that did not know who was asking, a model that denied tags it could not find, and queries that died past 5,000 assets.

Publishers:tenable.com

Reality

Evidence42
Adoption
Not scored
Hype gap+18
Incentives82
Confidence52
buildOne report1 publisher

Nobody Has Watched the Reviewer Say No: 89% of 204 Guards Were Never Shown to Fail

One developer counted the automated checks in his own repositories and found that only about one in nine could prove it was capable of rejecting anything.

Publishers:dev.to

Reality

Evidence30
Adoption15
Hype gap+22
Incentives35
Confidence45
buildOne report1 publisher

Code review's quality gate survives AI. Its apprenticeship does not.

An engineer at Snappfood watched pull requests get bigger and faster after adopting AI tools. The part of review that catches bugs still works; the part that moved knowledge has no author to draw from.

Publishers:dev.to

Reality

Evidence20
Adoption18
Hype gap+12
Incentives22
Confidence34
buildOne report1 publisher

A £40 refund and a £40,000 one look identical to a pre-execution guardrail

A dev.to post makes a narrow, useful point: agent hooks can read intent, and cost is not a property of intent. The check belongs where the ledger already is.

Publishers:dev.to

Reality

Evidence44
Adoption15
Hype gap−6
Incentives52
Confidence58
buildOne report1 publisher

Connecticut judge sanctions hidden prompt injection that no court AI was there to read

Judge Walter Spader Jr. found that no Connecticut court uses AI on filings, then sanctioned the litigant anyway. A clerk caught the size-3 white text by its spacing, not by scanning.

Publishers:dev.to

Reality

Evidence45
Adoption18
Hype gap+12
Incentives42
Confidence40
productOne report1 publisher

Three tools, three MRR numbers: the fix is a metric definition, not a better model

PostHog asked Claude, Cursor and its own assistant the same revenue question and got three answers. Its remedy was a governed catalog of definitions stored as ordinary SQL tables.

Publishers:posthog.com

Reality

Evidence34
Adoption21
Hype gap+22
Incentives78
Confidence42
buildOne report1 publisher

Test count told you nothing about the merge gate; 17 attempts to beat it told you something

The author of a now-public merge-gate core recounted his own suite: 22 tests in the evasion file, of which 17 are attacks and 5 exist to stop the gate being red all the time.

Publishers:dev.to

Reality

Evidence44
Adoption12
Hype gap−14
Incentives55
Confidence42
buildOne report1 publisher

A guard that only speaks in exit codes cannot tell you it stopped guarding

A PreToolUse hook on an AI coding agent returned "allow" for every file under a non-ASCII directory name, for weeks, with no log line and no exception.

Publishers:dev.to

Reality

Evidence63
Adoption12
Hype gap−5
Incentives42
Confidence55