AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: nextjs-15-server-actions-origin-attestation

Next.js 15 Server Action Distributed Edge Origin Attestation Invariant

Next.js 15 Server Actions mandate strict runtime Host, X-Forwarded-Host, and Origin header attestation to eliminate state-mutating request injection behind distributed CDNs and multi-tenant edge proxies. Relying on default host validation without explicit origin allowlisting permits cross-origin invocations and host-poisoning attacks across split-edge architectures.

Prohibited Anti-Pattern: Implicit Trust of Origin and Host Headers in Edge-Terminated Server Actions

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Server Action Distributed Edge Origin Attestation Invariant - Next.js 15 Server Actions mandate strict runtime Host, X-Forwarded-Host, and Origin header attestation to eliminate state-mutating request injection behind distributed CDNs and multi-tenant edge proxies. Relying on default host validation without explicit origin allowlisting permits cross-origin invocations and host-poisoning attacks across split-edge architectures.
globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, next.config.{ts,js,mjs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-server-actions-origin-attestation"
---

# Next.js 15 Server Action Distributed Edge Origin Attestation Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Implicit Trust of Origin and Host Headers in Edge-Terminated Server Actions

## System Constraints
You are a Principal Software Architect enforcing cryptographic and edge-aware origin attestation for Next.js 15 Server Actions. In multi-CDN and reverse-proxy deployments, Next.js action endpoints ('use server') are vulnerable to cross-origin forgery and host header poisoning if edge layers rewrite or mismatch incoming Origin and Host headers. You must mandate strict runtime attestation via next.config.ts serverActions.allowedOrigins and defense-in-depth runtime header verification wrappers on all mutating actions.

## Strict Guidelines
- Engineers MUST ALWAYS configure `experimental.serverActions.allowedOrigins` in `next.config.ts` when deploying behind CDNs, micro-frontends, or reverse proxies.
- Engineers MUST NOT rely solely on implicit framework-level CSRF tokens without explicit runtime verification of the `Origin` and `Host` / `X-Forwarded-Host` pairing for mutating Server Actions.
- Code MUST reject incoming Server Action requests where the `Origin` header protocol, hostname, or port diverges from the cryptographically resolved cluster domain allowlist.
- Services MUST extract action validation logic into an idempotent Higher-Order Action or Action Client middleware (e.g., using a hardened safe-action pipeline) prior to state mutations.
- Components NEVER execute raw, unwrapped `'use server'` directives directly inside client-interactive modules without going through verified action client boundaries.

## Bad vs Good Implementations
### Unprotected Server Action vs. Attested Safe-Action Boundary

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The Server Action trusts incoming requests implicitly. In distributed edge architectures where CDNs terminate TLS or forward non-standard Host headers, an attacker can trigger this mutating action via cross-origin POST requests or poisoned host boundaries without edge-level validation.
```typescript
// app/actions/update-billing.ts
'use server';

import { db } from '@/lib/db';
import { revalidatePath } from 'next/cache';

// CRITICAL FLAW: Invoked directly behind CDN edge without Origin/Host verification.
// If next.config.ts lacks allowedOrigins or edge rewrites Host, this is vulnerable
// to cross-origin execution and header poisoning in multi-tenant environments.
export async function updateBillingEmail(formData: FormData) {
  const email = formData.get('email') as string;
  const tenantId = formData.get('tenantId') as string;

  await db.tenant.update({
    where: { id: tenantId },
    data: { billingEmail: email },
  });

  revalidatePath('/settings/billing');
}
```

#### Production Standard (Correct)
> **Standard**: Enforces a defense-in-depth model: explicit `serverActions.allowedOrigins` in Next.js configuration combined with an imperative cryptographic origin assertion verifying header integrity and proxy consistency before state alteration.
```typescript
// next.config.ts
import type { NextConfig } from 'next';

const nextConfig: NextConfig = {
  experimental: {
    serverActions: {
      allowedOrigins: [
        'app.production.domain.com',
        'api.production.domain.com',
      ],
    },
  },
};
export default nextConfig;

// lib/safe-action.ts
import { headers } from 'next/headers';

const ALLOWED_HOSTS = new Set([
  'app.production.domain.com',
  'api.production.domain.com',
]);

export async function assertOriginInvariant(): Promise<void> {
  const headerList = await headers();
  const origin = headerList.get('origin');
  const host = headerList.get('x-forwarded-host') ?? headerList.get('host');

  if (!origin || !host) {
    throw new Error('Security Violation: Missing transport security headers.');
  }

  const parsedOrigin = new URL(origin);
  
  if (!ALLOWED_HOSTS.has(parsedOrigin.host) || !ALLOWED_HOSTS.has(host)) {
    throw new Error(`Security Violation: Untrusted origin [${parsedOrigin.host}] or host [${host}].`);
  }

  if (parsedOrigin.host !== host) {
    throw new Error('Security Violation: Origin/Host mismatch in edge proxy chain.');
  }
}

// app/actions/update-billing.ts
'use server';

import { db } from '@/lib/db';
import { assertOriginInvariant } from '@/lib/safe-action';
import { revalidatePath } from 'next/cache';

export async function updateBillingEmail(formData: FormData) {
  await assertOriginInvariant();

  const email = String(formData.get('email'));
  const tenantId = String(formData.get('tenantId'));

  await db.tenant.update({
    where: { id: tenantId },
    data: { billingEmail: email },
  });

  revalidatePath('/settings/billing');
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Fetch MCP Server
Validates HTTP headers and cross-origin responses during automated testing of Server Actions.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Next.js Security Auditor
CLI utility to lint Next.js server actions and verify allowedOrigins configuration against deployment architecture.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Server Action Distributed Edge Origin Attestation Invariant

Next.js 15 Server Action Distributed Edge Origin Attestation Invariant defines an industrial-grade behavioral standard for frontend engineering. Next.js 15 Server Actions mandate strict runtime Host, X-Forwarded-Host, and Origin header attestation to eliminate state-mutating request injection behind distributed CDNs and multi-tenant edge proxies. Relying on default host validation without explicit origin allowlisting permits cross-origin invocations and host-poisoning attacks across split-edge architectures. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Implicit Trust of Origin and Host Headers in Edge-Terminated Server Actions Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftImplicit Trust of Origin and Host Headers in Edge-Terminated Server ActionsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS configure `experimental.serverActions.allowedOrigins` in `next.config.ts` when deploying behind CDNs, micro-frontends, or reverse proxies.

Engineers MUST ALWAYS configure `experimental.serverActions.allowedOrigins` in `next.config.ts` when deploying behind CDNs, micro-frontends, or reverse proxies.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT rely solely on implicit framework-level CSRF tokens without explicit runtime verification of the `Origin` and `Host` / `X-Forwarded-Host` pairing for mutating Server Actions.

Engineers MUST NOT rely solely on implicit framework-level CSRF tokens without explicit runtime verification of the `Origin` and `Host` / `X-Forwarded-Host` pairing for mutating Server Actions.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code MUST reject incoming Server Action requests where the `Origin` header protocol, hostname, or port diverges from the cryptographically resolved cluster domain allowlist.

Code MUST reject incoming Server Action requests where the `Origin` header protocol, hostname, or port diverges from the cryptographically resolved cluster domain allowlist.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST extract action validation logic into an idempotent Higher-Order Action or Action Client middleware (e.g., using a hardened safe-action pipeline) prior to state mutations.

Services MUST extract action validation logic into an idempotent Higher-Order Action or Action Client middleware (e.g., using a hardened safe-action pipeline) prior to state mutations.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER execute raw, unwrapped `'use server'` directives directly inside client-interactive modules without going through verified action client boundaries.

Components NEVER execute raw, unwrapped `'use server'` directives directly inside client-interactive modules without going through verified action client boundaries.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Next.js 15 Server Action Distributed Edge Origin Attestation Invariant critical for AI coding assistants?

Next.js 15 Server Actions mandate strict runtime Host, X-Forwarded-Host, and Origin header attestation to eliminate state-mutating request injection behind distributed CDNs and multi-tenant edge proxies. Relying on default host validation without explicit origin allowlisting permits cross-origin invocations and host-poisoning attacks across split-edge architectures. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Implicit Trust of Origin and Host Headers in Edge-Terminated Server Actions) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Next.js