React 19 Server Actions Cryptographic Replay & Idempotency Standard

Q: How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unvalidated and Naked Server Actions Vulnerable to Distributed Replay Attacks and Double Mutations) 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.

React 19 Server Actions Cryptographic Replay & Idempotency Standard

--- description: React 19 Server Actions Cryptographic Replay & Idempotency Standard - Enforces cryptographically signed monotonic nonces and distributed atomic claim locks on React 19 Server Actions to eliminate double-execution, race conditions, and distributed replay attacks across edge runtimes. Mandates strict validation of ephemeral HMAC-signed action tokens before executing any state-mutating operation. 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-actions-replay-idempotency-standard" --- # React 19 Server Actions Cryptographic Replay & Idempotency Standard > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Unvalidated and Naked Server Actions Vulnerable to Distributed Replay Attacks and Double Mutations ## System Constraints You are a Principal Security Architect enforcing the React 19 Server Actions Cryptographic Replay & Idempotency Standard. React 19 Server Actions are public POST endpoints reachable outside the browser UI. You must reject any naked mutating Server Action that accepts unauthenticated or unsigned execution payloads. Enforce monotonic nonce validation, cryptographic signature verification (HMAC-SHA256), and atomic single-use token consumption via distributed cache primitives (e.g., Redis, Upstash) before allowing state mutations. ## Strict Guidelines - Engineers MUST ALWAYS cryptographically sign monotonic action tokens (nonce + timestamp + action identity) on initial form/component render and pass them as hidden fields or parameters to Server Actions. - Engineers MUST NOT rely solely on client-side state flags (e.g., isPending, disabled attributes) to prevent duplicate submissions or replay attacks. - Services MUST atomically claim and invalidate the token nonce using an atomic conditional write (e.g., Redis SET key value NX EX) prior to initiating any database mutation. - Code SHOULD enforce strict expiration windows (TTL <= 300 seconds) and clock skew verification on generated monotonic nonces to prevent long-tail replay vulnerabilities across edge nodes. - Components NEVER execute raw data mutations directly within un-scoped Server Actions without validating user session context alongside the cryptographic replay proof. ## Bad vs Good Implementations ### Naked Server Action without Replay Protection vs. Cryptographically Verified Monotonic Action #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The Server Action accepts raw mutation parameters with no cryptographic verification or idempotency token. A malicious actor can replay the captured HTTP POST request, or a network stutter can double-debit the balance before client state updates. ```typescript 'use server'; import { db } from '@/lib/db'; import { revalidatePath } from 'next/cache'; interface TransferPayload { recipientId: string; amountCents: number; } // VULNERABLE: Direct execution allows network replays and concurrent double-clicks export async function executeTransfer(payload: TransferPayload) { const user = await db.getCurrentUser(); if (!user) throw new Error('Unauthorized'); await db.account.decrementBalance(user.id, payload.amountCents); await db.account.incrementBalance(payload.recipientId, payload.amountCents); revalidatePath('/dashboard'); return { success: true }; } ``` #### Production Standard (Correct) > **Standard**: Enforces an HMAC-signed nonce bound to the user and action ID, validates temporal expiration, and claims the nonce atomically using Redis SET NX. Replay attempts will fail at the cryptographic or atomic lock stage. ```typescript 'use server'; import { db } from '@/lib/db'; import { redis } from '@/lib/redis'; import { verifyActionSignature } from '@/lib/crypto'; import { revalidatePath } from 'next/cache'; interface SecureTransferPayload { recipientId: string; amountCents: number; nonce: string; timestamp: number; signature: string; } const ACTION_ID = 'executeTransfer'; const NONCE_TTL_SECONDS = 300; export async function executeTransfer(payload: SecureTransferPayload) { const user = await db.getCurrentUser(); if (!user) throw new Error('Unauthorized'); // 1. Verify cryptographic HMAC signature const isValid = verifyActionSignature({ userId: user.id, actionId: ACTION_ID, nonce: payload.nonce, timestamp: payload.timestamp, signature: payload.signature }); if (!isValid) throw new Error('Invalid or forged action signature'); // 2. Reject tokens outside clock-skew tolerance window const now = Date.now(); if (Math.abs(now - payload.timestamp) > NONCE_TTL_SECONDS * 1000) { throw new Error('Action token expired or clock drift exceeded'); } // 3. Atomically consume monotonic nonce to guarantee single-execution const lockKey = `action_lock:${user.id}:${payload.nonce}`; const acquired = await redis.set(lockKey, 'CONSUMED', 'EX', NONCE_TTL_SECONDS, 'NX'); if (!acquired) { throw new Error('Replay detected or action currently processing'); } // 4. Safely execute business mutation inside transaction await db.$transaction(async (tx) => { await tx.account.decrementBalance(user.id, payload.amountCents); await tx.account.incrementBalance(payload.recipientId, payload.amountCents); }); revalidatePath('/dashboard'); return { success: true }; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Actions Cryptographic Replay & Idempotency Standard

React 19 Server Actions Cryptographic Replay & Idempotency Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces cryptographically signed monotonic nonces and distributed atomic claim locks on React 19 Server Actions to eliminate double-execution, race conditions, and distributed replay attacks across edge runtimes. Mandates strict validation of ephemeral HMAC-signed action tokens before executing any state-mutating operation. 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: Unvalidated and Naked Server Actions Vulnerable to Distributed Replay Attacks and Double Mutations 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	Unvalidated and Naked Server Actions Vulnerable to Distributed Replay Attacks and Double Mutations	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 cryptographically sign monotonic action tokens (nonce + timestamp + action identity) on initial form/component render and pass them as hidden fields or parameters to Server Actions.

Engineers MUST ALWAYS cryptographically sign monotonic action tokens (nonce + timestamp + action identity) on initial form/component render and pass them as hidden fields or parameters to 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.