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: react19-server-component-tainted-object-boundary

React 19 Server Component Tainted Object Invariant

Enforces strict boundary isolation for sensitive server-side payloads using React 19 experimental taint APIs. Guarantees that raw database models, authorization secrets, and sensitive tokens cannot be serialized and passed across the Server-to-Client component boundary, mandating explicit projection to client-safe Data Transfer Objects (DTOs).

Prohibited Anti-Pattern: Passing Untainted Raw Server Entities or Secrets Directly Across the RSC Serialization Boundary

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Server Component Tainted Object Invariant - Enforces strict boundary isolation for sensitive server-side payloads using React 19 experimental taint APIs. Guarantees that raw database models, authorization secrets, and sensitive tokens cannot be serialized and passed across the Server-to-Client component boundary, mandating explicit projection to client-safe Data Transfer Objects (DTOs).
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/react19-server-component-tainted-object-boundary"
---

# React 19 Server Component Tainted Object Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Passing Untainted Raw Server Entities or Secrets Directly Across the RSC Serialization Boundary

## System Constraints
You are a Principal Software Architect enforcing the React 19 Server Component Tainted Object Invariant. Mandate that all raw data access layer (DAL) entities containing sensitive or internal fields, as well as server credentials, are actively protected using React 19's experimental_taintObjectReference and experimental_taintUniqueValue. Prevent accidental prop leakage to Client Components.

## Strict Guidelines
- Engineers MUST ALWAYS invoke experimental_taintObjectReference at the Data Access Layer (DAL) immediately upon instantiating or fetching raw domain entities containing sensitive metadata, hashes, or PII.
- Engineers MUST ALWAYS invoke experimental_taintUniqueValue for individual sensitive scalar values such as environment secret keys, JWT signing keys, and payment gateway tokens to prevent leakage even if copied into other objects.
- Engineers MUST NOT pass raw database or ORM entities directly as props to Client Components ('use client') or return them directly from Server Actions.
- Code MUST explicitly construct separate, allowlisted Data Transfer Objects (DTOs) with primitive scalar fields before passing data to Client Components.
- Services MUST declare 'server-only' at the module level whenever tainting functions or raw database clients are initialized to guarantee runtime exclusion from client bundles.
- Components NEVER rely on TypeScript type omission (e.g., Omit<User, 'passwordHash'>) alone to enforce runtime security boundaries across RSC serialization.

## Bad vs Good Implementations
### Data Access Layer: Untainted Entity vs. React 19 Tainted Object Reference

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The raw database entity is returned directly without registering a taint invariant. If a developer accidentally passes this object to a Client Component prop, React will serialize the entire object including sensitive hashes into the public HTML/RSC flight payload.
```typescript
import { db } from '@/lib/db';

// ANTI-PATTERN: Raw database record contains sensitive fields
// (e.g., passwordHash, stripeCustomerId) with no taint guardrail.
export async function getUserProfile(userId: string) {
  const user = await db.user.findUnique({
    where: { id: userId },
  });

  // Accidental exposure: Passing 'user' to a Client Component
  // will serialize all fields (including hashes) into the flight payload.
  return user;
}
```

#### Production Standard (Correct)
> **Standard**: experimental_taintObjectReference blocks the raw record from ever being serialized across the server/client boundary, throwing a runtime build or render error if attempted. The DAL explicitly projects and returns a minimal, client-safe DTO.
```typescript
import 'server-only';
import { experimental_taintObjectReference, experimental_taintUniqueValue } from 'react';
import { db } from '@/lib/db';

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

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

  if (!user) return null;

  // INVARIANT: Block the entire raw object from serialization to Client Components
  experimental_taintObjectReference(
    'Do not pass the raw User entity to the client. Map to ClientSafeUserProfile first.',
    user
  );

  // INVARIANT: Taint unique sensitive scalar strings to prevent extraction leaks
  if (user.stripeCustomerId) {
    experimental_taintUniqueValue(
      'Do not expose Stripe Customer IDs to client bundles.',
      user,
      user.stripeCustomerId
    );
  }

  // Return an explicitly projected, untainted 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.

ast-grep MCP Server
Performs structural AST searches across React Server Components to verify taint calls on database entities.
Recommended Agent Skills (askills.dev)

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

react-compiler-linter
Validates React 19 server/client boundaries and flags untainted server-only data crossings.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Component Tainted Object Invariant

React 19 Server Component Tainted Object Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict boundary isolation for sensitive server-side payloads using React 19 experimental taint APIs. Guarantees that raw database models, authorization secrets, and sensitive tokens cannot be serialized and passed across the Server-to-Client component boundary, mandating explicit projection to client-safe Data Transfer Objects (DTOs). 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: Passing Untainted Raw Server Entities or Secrets Directly Across the RSC 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftPassing Untainted Raw Server Entities or Secrets Directly Across the RSC Serialization BoundaryCritical
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 invoke experimental_taintObjectReference at the Data Access Layer (DAL) immediately upon instantiating or fetching raw domain entities containing sensitive metadata, hashes, or PII.

Engineers MUST ALWAYS invoke experimental_taintObjectReference at the Data Access Layer (DAL) immediately upon instantiating or fetching raw domain entities containing sensitive metadata, hashes, or PII.

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_taintUniqueValue for individual sensitive scalar values such as environment secret keys, JWT signing keys, and payment gateway tokens to prevent leakage even if copied into other objects.

Engineers MUST ALWAYS invoke experimental_taintUniqueValue for individual sensitive scalar values such as environment secret keys, JWT signing keys, and payment gateway tokens to prevent leakage even if copied into other objects.

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 NOT pass raw database or ORM entities directly as props to Client Components ('use client') or return them directly from Server Actions.

Engineers MUST NOT pass raw database or ORM entities directly as props to Client Components ('use client') or return them directly from 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.
4

Code MUST explicitly construct separate, allowlisted Data Transfer Objects (DTOs) with primitive scalar fields before passing data to Client Components.

Code MUST explicitly construct separate, allowlisted Data Transfer Objects (DTOs) with primitive scalar fields before passing data to Client Components.

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

Services MUST declare 'server-only' at the module level whenever tainting functions or raw database clients are initialized to guarantee runtime exclusion from client bundles.

Services MUST declare 'server-only' at the module level whenever tainting functions or raw database clients are initialized to guarantee runtime exclusion from client bundles.

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

Components NEVER rely on TypeScript type omission (e.g., Omit<User, 'passwordHash'>) alone to enforce runtime security boundaries across RSC serialization.

Components NEVER rely on TypeScript type omission (e.g., Omit<User, 'passwordHash'>) alone to enforce runtime security boundaries across RSC serialization.

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 Component Tainted Object Invariant critical for AI coding assistants?

Enforces strict boundary isolation for sensitive server-side payloads using React 19 experimental taint APIs. Guarantees that raw database models, authorization secrets, and sensitive tokens cannot be serialized and passed across the Server-to-Client component boundary, mandating explicit projection to client-safe Data Transfer Objects (DTOs). 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 (Passing Untainted Raw Server Entities or Secrets Directly Across the RSC Serialization Boundary) 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