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: react-19-rsc-taint-boundary-standard-react-19-server--197

React 19 Server Components Cryptographic Object Taint Boundary Standard

Enforces strict cryptographic serialization boundaries across React 19 Server Components using experimental_taintObjectReference and experimental_taintUniqueValue primitives. Guarantees that raw data layer entities, credentials, and PII are structurally blocked from crossing RSC serialization boundaries into client bundles. Prevents silent data exfiltration by failing fast during RSC payload streaming if tainted memory references or scalar values are referenced in client props.

Prohibited Anti-Pattern: Accidental Client Serialization of Raw DB Entities, Internal Auth Tokens, or PII Across RSC Boundaries

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Server Components Cryptographic Object Taint Boundary Standard - Enforces strict cryptographic serialization boundaries across React 19 Server Components using experimental_taintObjectReference and experimental_taintUniqueValue primitives. Guarantees that raw data layer entities, credentials, and PII are structurally blocked from crossing RSC serialization boundaries into client bundles. Prevents silent data exfiltration by failing fast during RSC payload streaming if tainted memory references or scalar values are referenced in client props.
globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, lib/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/react-19-rsc-taint-boundary-standard-react-19-server--197"
---

# React 19 Server Components Cryptographic Object Taint Boundary Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Accidental Client Serialization of Raw DB Entities, Internal Auth Tokens, or PII Across RSC Boundaries

## System Constraints
You are a Principal Software Architect enforcing zero-leakage security boundaries in React 19 Server Components (RSC). Your mandate is to prevent accidental serialization of sensitive data (database credentials, authorization tokens, passwords, SSNs, and raw ORM entities) to client-side bundles. You must enforce the usage of `experimental_taintObjectReference` and `experimental_taintUniqueValue` at the Data Access Layer (DAL), enforce 'server-only' isolation, and mandate sanitized Data Transfer Objects (DTOs) for all client component props.

## Strict Guidelines
- Engineers MUST ALWAYS isolate data access modules using the 'server-only' package import at the file root to prevent accidental client bundling.
- Engineers MUST ALWAYS invoke `experimental_taintObjectReference` on raw domain models, database records, and secret configurations immediately upon instantiation or retrieval from persistence layers.
- Engineers MUST ALWAYS invoke `experimental_taintUniqueValue` on sensitive scalar fields (e.g., password hashes, personal API keys, session tokens, national IDs) linking them to their source object reference.
- Engineers MUST NOT pass raw database entities, ORM query results (Prisma, Drizzle, Kysely), or untrusted backend response objects directly to Client Component props.
- Code SHOULD project strictly validated, explicit Data Transfer Objects (DTOs) containing only the minimal public fields required by the rendering UI before passing props across the RSC boundary.
- Services MUST execute tainting within the innermost Data Access Layer (DAL) functions before returning entities to Server Components or Server Actions.
- Components NEVER accept tainted records without explicit field destructuring into explicitly typed client-safe interface contracts.

## Bad vs Good Implementations
### Data Access Layer (DAL) Taint Protection vs Unsafe Entity Leaking

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The raw user entity containing sensitive fields (passwordHash, stripeCustomerId) is returned unmodified without tainting. If a developer accidentally renders `<UserProfile user={user} />` where UserProfile is a Client Component ('use client'), all sensitive fields are emitted into the client bundle payload.
```typescript
// lib/dal/user.ts
import { db } from '@/lib/db';

export async function getUserAccount(userId: string) {
  // Anti-pattern: Returns raw database record without tainting or server boundary isolation.
  // If passed directly to a Client Component, passwordHash, stripeCustomerId, and internal
  // metadata will be serialized verbatim into the flight payload (RSC payload JSON in the HTML).
  const user = await db.user.findUnique({
    where: { id: userId },
  });

  return user;
}
```

#### Production Standard (Correct)
> **Standard**: The module declares 'server-only', invokes `experimental_taintObjectReference` to block the root object from RSC serialization, and applies `experimental_taintUniqueValue` to prevent string/token extraction. If any server component attempts to pass the raw record or scalar secrets across the client boundary, React aborts with a runtime exception.
```typescript
// lib/dal/user.ts
import 'server-only';
import { experimental_taintObjectReference, experimental_taintUniqueValue } from 'react';
import { db } from '@/lib/db';

export interface PublicUserDTO {
  id: string;
  name: string;
  avatarUrl: string | null;
}

export async function getUserAccount(userId: string): Promise<PublicUserDTO | null> {
  const user = await db.user.findUnique({
    where: { id: userId },
  });

  if (!user) return null;

  // Invariant: Cryptographically taint the raw database entity reference
  experimental_taintObjectReference(
    'Do not pass raw User database entities to the client. Project to PublicUserDTO.',
    user
  );

  // Invariant: Cryptographically taint unique scalar credentials and tokens
  if (user.passwordHash) {
    experimental_taintUniqueValue(
      'Do not pass password hashes to the client.',
      user,
      user.passwordHash
    );
  }
  if (user.stripeCustomerId) {
    experimental_taintUniqueValue(
      'Do not pass payment customer IDs to the client.',
      user,
      user.stripeCustomerId
    );
  }

  // Explicit projection to Client-Safe DTO
  return {
    id: user.id,
    name: user.name,
    avatarUrl: user.avatarUrl,
  };
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

ESLint RSC Security MCP
Static analysis MCP server verifying RSC boundaries, server-only imports, and React 19 taint API adoption.
Recommended Agent Skills (askills.dev)

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

RSC Boundary Auditor
AST inspector that checks server actions and component prop serialization trees for untainted database entities.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Components Cryptographic Object Taint Boundary Standard

React 19 Server Components Cryptographic Object Taint Boundary Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict cryptographic serialization boundaries across React 19 Server Components using experimental_taintObjectReference and experimental_taintUniqueValue primitives. Guarantees that raw data layer entities, credentials, and PII are structurally blocked from crossing RSC serialization boundaries into client bundles. Prevents silent data exfiltration by failing fast during RSC payload streaming if tainted memory references or scalar values are referenced in client props. 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: Accidental Client Serialization of Raw DB Entities, Internal Auth Tokens, or PII Across RSC Boundaries 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 DriftAccidental Client Serialization of Raw DB Entities, Internal Auth Tokens, or PII Across RSC BoundariesCritical
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 isolate data access modules using the 'server-only' package import at the file root to prevent accidental client bundling.

Engineers MUST ALWAYS isolate data access modules using the 'server-only' package import at the file root to prevent accidental client bundling.

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 ALWAYS invoke `experimental_taintObjectReference` on raw domain models, database records, and secret configurations immediately upon instantiation or retrieval from persistence layers.

Engineers MUST ALWAYS invoke `experimental_taintObjectReference` on raw domain models, database records, and secret configurations immediately upon instantiation or retrieval from persistence layers.

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

Engineers MUST ALWAYS invoke `experimental_taintUniqueValue` on sensitive scalar fields (e.g., password hashes, personal API keys, session tokens, national IDs) linking them to their source object reference.

Engineers MUST ALWAYS invoke `experimental_taintUniqueValue` on sensitive scalar fields (e.g., password hashes, personal API keys, session tokens, national IDs) linking them to their source object reference.

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

Engineers MUST NOT pass raw database entities, ORM query results (Prisma, Drizzle, Kysely), or untrusted backend response objects directly to Client Component props.

Engineers MUST NOT pass raw database entities, ORM query results (Prisma, Drizzle, Kysely), or untrusted backend response objects directly to Client Component props.

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

Code SHOULD project strictly validated, explicit Data Transfer Objects (DTOs) containing only the minimal public fields required by the rendering UI before passing props across the RSC boundary.

Code SHOULD project strictly validated, explicit Data Transfer Objects (DTOs) containing only the minimal public fields required by the rendering UI before passing props across the RSC boundary.

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.
6

Services MUST execute tainting within the innermost Data Access Layer (DAL) functions before returning entities to Server Components or Server Actions.

Services MUST execute tainting within the innermost Data Access Layer (DAL) functions before returning entities to Server Components or 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.
7

Components NEVER accept tainted records without explicit field destructuring into explicitly typed client-safe interface contracts.

Components NEVER accept tainted records without explicit field destructuring into explicitly typed client-safe interface contracts.

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 React 19 Server Components Cryptographic Object Taint Boundary Standard critical for AI coding assistants?

Enforces strict cryptographic serialization boundaries across React 19 Server Components using experimental_taintObjectReference and experimental_taintUniqueValue primitives. Guarantees that raw data layer entities, credentials, and PII are structurally blocked from crossing RSC serialization boundaries into client bundles. Prevents silent data exfiltration by failing fast during RSC payload streaming if tainted memory references or scalar values are referenced in client props. 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 (Accidental Client Serialization of Raw DB Entities, Internal Auth Tokens, or PII Across RSC Boundaries) 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

React