React 19 Server Actions: Cryptographic Replay Barrier & Monotonic Token Invariant

--- description: React 19 Server Actions: Cryptographic Replay Barrier & Monotonic Token Invariant - Enforces single-use cryptographic idempotency tokens bound to server action payloads in React 19 to neutralize double-submit race conditions and network replay hazards. Protects progressive enhancement forms and direct client RPC invocations by atomically consuming tokens via transactional storage before executing state-changing operations. globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/react-19-server-action-cryptographic-replay-barrier" --- # React 19 Server Actions: Cryptographic Replay Barrier & Monotonic Token Invariant > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Naked Server Actions Executing Unchecked State Mutations Subject to Double-Submit and Replay Cascades ## System Constraints You are a Principal Software Architect enforcing cryptographic replay barriers and strict idempotency for React 19 Server Actions. Mandate that every stateful mutation bound to a Server Action implements a cryptographically signed, single-use monotonic barrier token that is consumed atomically prior to execution. ## Strict Guidelines - Engineers MUST ALWAYS generate a cryptographically secure, monotonic nonce or HMAC-signed idempotency token when rendering forms or views executing stateful React 19 Server Actions. - Engineers MUST NOT rely on client-side button disabling (`disabled={isPending}`) as a concurrency or replay security boundary. - Services MUST atomically claim and consume the idempotency token (e.g., using Redis `SETNX` or an atomic relational database transaction with unique constraints) BEFORE executing any side effect. - Components NEVER expose unverified raw action endpoints that alter persistent domain state without validating both the authenticated actor session and the one-time action token. - Code SHOULD gracefully handle duplicate replay submissions by either returning cached deterministic responses or rejecting with an explicit HTTP 409 / state conflict result rather than failing silently or crashing. ## Bad vs Good Implementations ### React 19 Server Action Idempotency Barrier #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The server action lacks cryptographic replay prevention and idempotency safeguards. In flaky network conditions or under progressive enhancement (where client JS has not yet hydrated), duplicate form submissions trigger multiple concurrent balance decrements. ```typescript // app/actions/transfer.ts 'use server'; import { db } from '@/lib/db'; import { revalidatePath } from 'next/cache'; // VULNERABLE: Direct mutation without replay protection or single-use verification. // Double clicks, network retries, or progressive enhancement re-submissions cause duplicate execution. export async function executeTransfer(formData: FormData) { const recipientId = formData.get('recipientId') as string; const amount = Number(formData.get('amount')); // Race hazard: Concurrent requests execute multiple times await db.account.decrementBalance(amount); await db.account.incrementBalance(recipientId, amount); revalidatePath('/dashboard'); return { success: true }; } ``` #### Production Standard (Correct) > **Standard**: Implements a strict cryptographic replay barrier. An HMAC/signed barrier token is extracted, cryptographically verified, and atomically claimed using a monotonic single-use check (Redis NX lock) before any side-effect or transaction begins. ```typescript // app/actions/transfer.ts 'use server'; import { db } from '@/lib/db'; import { redis } from '@/lib/redis'; import { verifyActionToken } from '@/lib/crypto'; import { revalidatePath } from 'next/cache'; export async function executeTransfer(prevState: unknown, formData: FormData) { const token = formData.get('__action_barrier_token'); const recipientId = formData.get('recipientId'); const amount = Number(formData.get('amount')); if (typeof token !== 'string' || !recipientId || isNaN(amount) || amount <= 0) { return { success: false, error: 'INVALID_PAYLOAD' }; } // 1. Cryptographically verify signature and payload integrity const payload = await verifyActionToken(token); if (!payload.valid || payload.action !== 'executeTransfer') { return { success: false, error: 'FORBIDDEN_REPLAY_DETECTED' }; } // 2. Monotonic single-use lock: atomically claim token with TTL const acquired = await redis.set(`barrier:${payload.tokenId}`, 'LOCKED', 'EX', 300, 'NX'); if (!acquired) { return { success: false, error: 'CONCURRENT_MUTATION_REJECTED' }; } // 3. Execute isolated mutation within transaction try { await db.$transaction(async (tx) => { await tx.account.decrementBalance(amount); await tx.account.incrementBalance(String(recipientId), amount); }); } catch (error) { // Unlock on failure to allow deliberate retry if applicable await redis.del(`barrier:${payload.tokenId}`); throw error; } revalidatePath('/dashboard'); return { success: true, error: null }; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Actions: Cryptographic Replay Barrier & Monotonic Token Invariant

React 19 Server Actions: Cryptographic Replay Barrier & Monotonic Token Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces single-use cryptographic idempotency tokens bound to server action payloads in React 19 to neutralize double-submit race conditions and network replay hazards. Protects progressive enhancement forms and direct client RPC invocations by atomically consuming tokens via transactional storage before executing state-changing operations. 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: Naked Server Actions Executing Unchecked State Mutations Subject to Double-Submit and Replay Cascades 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Naked Server Actions Executing Unchecked State Mutations Subject to Double-Submit and Replay Cascades	Critical	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 Inconsistency	AI 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:

Engineers MUST ALWAYS generate a cryptographically secure, monotonic nonce or HMAC-signed idempotency token when rendering forms or views executing stateful React 19 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.