Enforce React 19 Taint Boundaries for Server Actions and Client Tree Props

--- description: Enforce React 19 Taint Boundaries for Server Actions and Client Tree Props - Mandates compile-time isolation and runtime taint protections using React 19 taint APIs (experimental_taintObjectReference, experimental_taintUniqueValue) across Server Component boundaries and Server Action responses. Prohibits passing raw database records, sensitive environment variables, or cryptographically private tokens to Client Components. globs: app/**/*.{ts,tsx}, src/**/*.{ts,tsx}, lib/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/react-19-server-action-taint-boundary-protection" --- # Enforce React 19 Taint Boundaries for Server Actions and Client Tree Props > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Returning Raw ORM Entities or Unsanitized Secrets from Server Actions Across the RSC Client Serialization Boundary ## System Constraints You are a Principal Security and Frontend Architect enforcing React 19 Server Action Tainted Object Boundaries. You must ensure that no sensitive server-side objects, encryption keys, PII, or raw database entities are serialized and transmitted across the React Server Component (RSC) wire boundary into Client Components. Enforce strict DTO projection and React taint registration. ## Strict Guidelines - Engineers MUST ALWAYS register raw database entities and secret-bearing objects using 'experimental_taintObjectReference' or 'experimental_taintUniqueValue' at the server data access layer. - Engineers MUST NOT directly return unprojected ORM entities, Prisma/Drizzle records, or session models from Server Actions to the caller. - Code MUST explicitly project server-side domain models into strictly typed Data Transfer Objects (DTOs) before passing them as Client Component props or Server Action return values. - Services handling credentials, private keys, or API secrets MUST import 'server-only' to guarantee build-time failure if inadvertently imported into client bundles. - Components and Server Actions NEVER expose raw user identity payloads containing password hashes, MFA secrets, stripe customer tokens, or internal database metadata. ## Bad vs Good Implementations ### Tainting Raw User Model and Projecting DTOs Across Server Action Boundaries #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Returning raw ORM entities directly across the Server Action boundary serializes sensitive internal fields (password hashes, provider tokens, internal IDs) directly into the browser payload, creating a high-severity data leakage vulnerability. ```typescript 'use server'; import { db } from '@/lib/db'; // ANTI-PATTERN: Leaks passwordHash, stripeCustomerId, and audit metadata to the client export async function updateUserProfileAction(userId: string, formData: FormData) { const name = formData.get('name') as string; const updatedUser = await db.user.update({ where: { id: userId }, data: { name }, }); // Raw database record returned across serialization boundary return { success: true, user: updatedUser }; } ``` #### Production Standard (Correct) > **Standard**: Applies experimental_taintObjectReference to the raw user entity, causing React to throw an immediate runtime error if the object is passed into a client tree. Projects an explicit, strongly typed DTO containing only public fields. ```typescript 'use server'; import 'server-only'; import { experimental_taintObjectReference } from 'react'; import { db } from '@/lib/db'; import { z } from 'zod'; interface UserProfileDTO { id: string; name: string; email: string; } export async function updateUserProfileAction(userId: string, formData: FormData): Promise<{ success: boolean; user: UserProfileDTO }> { const name = String(formData.get('name') || ''); const rawUser = await db.user.update({ where: { id: userId }, data: { name }, }); // Invariant: Mark sensitive entity as tainted at runtime experimental_taintObjectReference( 'Do not pass the raw User database object to the client. Map to a UserProfileDTO instead.', rawUser ); // Strictly project to safe DTO boundary const safeProfile: UserProfileDTO = { id: rawUser.id, name: rawUser.name, email: rawUser.email, }; return { success: true, user: safeProfile }; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Enforce React 19 Taint Boundaries for Server Actions and Client Tree Props

Enforce React 19 Taint Boundaries for Server Actions and Client Tree Props defines an industrial-grade behavioral standard for frontend engineering. Mandates compile-time isolation and runtime taint protections using React 19 taint APIs (experimental_taintObjectReference, experimental_taintUniqueValue) across Server Component boundaries and Server Action responses. Prohibits passing raw database records, sensitive environment variables, or cryptographically private tokens to Client Components. 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: Returning Raw ORM Entities or Unsanitized Secrets from Server Actions Across the RSC Client Serialization Boundary 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	Returning Raw ORM Entities or Unsanitized Secrets from Server Actions Across the RSC Client Serialization Boundary	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 register raw database entities and secret-bearing objects using 'experimental_taintObjectReference' or 'experimental_taintUniqueValue' at the server data access layer.

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.