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-server-action-multitenant-context-isolation

React 19 Server Action Multi-Tenant Context Poisoning Invariant

Enforces strict request-scoped isolation in React 19 Server Actions using immutable AsyncLocalStorage to prevent cross-tenant data leaks and state poisoning during concurrent asynchronous executions. Prohibits global singleton mutations and client-supplied tenant identifiers as authoritative context.

Prohibited Anti-Pattern: Cross-tenant state bleeding via module-scoped state or client-spoofed tenant parameters in React 19 Server Actions.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Server Action Multi-Tenant Context Poisoning Invariant - Enforces strict request-scoped isolation in React 19 Server Actions using immutable AsyncLocalStorage to prevent cross-tenant data leaks and state poisoning during concurrent asynchronous executions. Prohibits global singleton mutations and client-supplied tenant identifiers as authoritative context.
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-multitenant-context-isolation"
---

# React 19 Server Action Multi-Tenant Context Poisoning Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Cross-tenant state bleeding via module-scoped state or client-spoofed tenant parameters in React 19 Server Actions.

## System Constraints
You are a Principal Security Architect enforcing React 19 Server Action Multi-Tenant Isolation Invariants. React 19 Server Actions execute in long-lived Node.js/Edge worker runtimes where module-level state and unisolated async continuations cause catastrophic cross-tenant context poisoning. You must mandate immutable AsyncLocalStorage boundaries and reject any pattern relying on client-provided tenant identifiers or global state mutation.

## Strict Guidelines
- Engineers MUST ALWAYS resolve tenant identity server-side from cryptographically verified sessions, never from client-supplied Server Action parameters.
- Engineers MUST NOT store tenant context, user claims, or database transaction handles in module-scoped variables or outer-scope singletons.
- Code MUST execute all tenant-bound operations inside an AsyncLocalStorage.run() scope with an Object.freeze-protected context.
- Services MUST validate that AsyncLocalStorage.getStore() returns an active, valid tenant context prior to dispatching any database query or cache mutation.
- Components NEVER pass tenant identifiers as hidden form fields or action arguments when executing authenticated mutations.

## Bad vs Good Implementations
### Mitigating Cross-Tenant Poisoning via Immutable AsyncLocalStorage Guardrail

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using module-level variables (ambientTenantId) in server actions causes cross-request race conditions where concurrent requests overwrite each other's tenant state. Furthermore, accepting tenantId from form data allows untrusted clients to mutate other tenants' records.
```typescript
// BAD: Module-level shared mutable state and client-spoofed tenantId
let ambientTenantId: string | null = null;

export async function updateTenantBilling(formData: FormData) {
  'use server';
  // CRITICAL VULNERABILITY: Tenant ID trusted directly from client payload
  const clientTenantId = formData.get('tenantId') as string;
  ambientTenantId = clientTenantId; // Leaks across concurrent requests in Node worker

  await new Promise((resolve) => setTimeout(resolve, 50)); // Simulates async I/O

  // Catastrophic data bleed: ambientTenantId may have been overwritten by another request
  await db.execute('UPDATE accounts SET plan = $1 WHERE tenant_id = $2', [
    formData.get('plan'),
    ambientTenantId,
  ]);
}
```

#### Production Standard (Correct)
> **Standard**: Guarantees re-entrant isolation using Node's AsyncLocalStorage wrapped with Object.freeze. Tenant identity is resolved strictly from the verified server-side session, completely eliminating spoofing and concurrent worker cross-talk.
```typescript
// GOOD: Immutable AsyncLocalStorage with authoritative session extraction
import { AsyncLocalStorage } from 'node:async_hooks';
import { verifySession } from '@/lib/auth';

interface TenantContext {
  readonly tenantId: string;
  readonly userId: string;
}

export const tenantStore = new AsyncLocalStorage<TenantContext>();

export async function updateTenantBilling(formData: FormData) {
  'use server';
  const session = await verifySession(); // Authoritative server-side identity
  if (!session?.tenantId) {
    throw new Error('Unauthorized: Invalid tenant session');
  }

  const immutableContext: TenantContext = Object.freeze({
    tenantId: session.tenantId,
    userId: session.userId,
  });

  return tenantStore.run(immutableContext, async () => {
    const activeContext = tenantStore.getStore();
    if (!activeContext) {
      throw new Error('Invariant Violation: Tenant context lost in async stack');
    }

    return await db.execute(
      'UPDATE accounts SET plan = $1 WHERE tenant_id = $2',
      [formData.get('plan'), activeContext.tenantId]
    );
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

ESLint Security Inspector
Validates that server actions do not reference outer-scope mutable variables or trust client-side tenant parameters.
Recommended Agent Skills (askills.dev)

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

React 19 Server Action Security Auditor
CLI tool to scan for shared state anti-patterns and AsyncLocalStorage leaks in React Server Components and Actions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Action Multi-Tenant Context Poisoning Invariant

React 19 Server Action Multi-Tenant Context Poisoning Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict request-scoped isolation in React 19 Server Actions using immutable AsyncLocalStorage to prevent cross-tenant data leaks and state poisoning during concurrent asynchronous executions. Prohibits global singleton mutations and client-supplied tenant identifiers as authoritative context. 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: Cross-tenant state bleeding via module-scoped state or client-spoofed tenant parameters in React 19 Server Actions. 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 DriftCross-tenant state bleeding via module-scoped state or client-spoofed tenant parameters in React 19 Server Actions.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 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 resolve tenant identity server-side from cryptographically verified sessions, never from client-supplied Server Action parameters.

Engineers MUST ALWAYS resolve tenant identity server-side from cryptographically verified sessions, never from client-supplied Server Action parameters.

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 NOT store tenant context, user claims, or database transaction handles in module-scoped variables or outer-scope singletons.

Engineers MUST NOT store tenant context, user claims, or database transaction handles in module-scoped variables or outer-scope singletons.

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

Code MUST execute all tenant-bound operations inside an AsyncLocalStorage.run() scope with an Object.freeze-protected context.

Code MUST execute all tenant-bound operations inside an AsyncLocalStorage.run() scope with an Object.freeze-protected context.

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

Services MUST validate that AsyncLocalStorage.getStore() returns an active, valid tenant context prior to dispatching any database query or cache mutation.

Services MUST validate that AsyncLocalStorage.getStore() returns an active, valid tenant context prior to dispatching any database query or cache mutation.

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

Components NEVER pass tenant identifiers as hidden form fields or action arguments when executing authenticated mutations.

Components NEVER pass tenant identifiers as hidden form fields or action arguments when executing authenticated mutations.

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 Action Multi-Tenant Context Poisoning Invariant critical for AI coding assistants?

Enforces strict request-scoped isolation in React 19 Server Actions using immutable AsyncLocalStorage to prevent cross-tenant data leaks and state poisoning during concurrent asynchronous executions. Prohibits global singleton mutations and client-supplied tenant identifiers as authoritative context. 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 (Cross-tenant state bleeding via module-scoped state or client-spoofed tenant parameters in React 19 Server Actions.) 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