Three reasons, each of which I could show on Next.js 16.4.5 (next build && next start).
Coverage is a path pattern. Proxy runs only where matcher says, but the things worth protecting aren't paths. A Server Action is a POST to whichever page renders it. With matcher: ['/dashboard/:path*'], an action used by /dashboard and also imported by the public home page ran with no cookie when posted to /, while the same call to /dashboard got a 307 to /login. The docs' own auth matcher excludes /api, so every route handler is uncovered unless it checks. The Proxy docs warn that moving an action or editing the matcher "can silently remove Proxy coverage".
It sees the request, not the resource. Proxy can tell that a session cookie exists and is validly signed. It can't tell whether user 7 may delete project 42; that needs the record. A database lookup there would run on every matched request, including each <Link> prefetch, so the docs limit Proxy to optimistic checks from the cookie.
It's a routing layer, and routing has bugs. CVE-2025-29927 (2025) let a request carrying the internal x-middleware-subrequest header skip middleware entirely. In 2026, advisories covered prefetch-segment .rsc URLs, injected route params and a Turbopack i18n case, each reaching protected content without the check.
So: keep Proxy for redirecting signed-out users and protecting static pages shared by all users (the case the docs give it). Put the real check in a data access layer: every Server Action, route handler and data function verifies the session and authorizes the specific resource. Then a matcher mistake or a routing bug costs a redirect, not data.