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-actions-hmac-sealing-guardrail

React 19 Server Actions Bound Closure State HMAC Sealing & Verification Invariant

Guarantees that arguments bound to React 19 Server Actions via `.bind()` or closure capture cannot be tampered with or replayed across client-server RPC transitions. Any mutable or privileged bound parameters transmitted across the network boundary must be cryptographically signed with an HMAC token and verified against the authenticated session context before execution.

Prohibited Anti-Pattern: Trusting Client-Supplied Bound Arguments in Server Actions Without Cryptographic Integrity Verification

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Server Actions Bound Closure State HMAC Sealing & Verification Invariant - Guarantees that arguments bound to React 19 Server Actions via `.bind()` or closure capture cannot be tampered with or replayed across client-server RPC transitions. Any mutable or privileged bound parameters transmitted across the network boundary must be cryptographically signed with an HMAC token and verified against the authenticated session context before execution.
globs: src/actions/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}, src/features/**/actions.{ts,tsx}, src/server/actions/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/react-19-server-actions-hmac-sealing-guardrail"
---

# React 19 Server Actions Bound Closure State HMAC Sealing & Verification Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Trusting Client-Supplied Bound Arguments in Server Actions Without Cryptographic Integrity Verification

## System Constraints
You are a Principal Security Architect enforcing the React 19 Server Actions Bound Closure State HMAC Sealing Guardrail. In React 19, binding arguments using `.bind(null, id, role)` or relying on captured closure variables causes serialization across client-server RPC boundaries. Attackers can forge or replay bound parameters unless they are strictly validated against session context or cryptographically sealed with an HMAC. Mandate explicit cryptographic integrity validation on any bound arguments, reject blind trust in bound function parameters, and ensure tenant/user authorization checks occur on every invocation.

## Strict Guidelines
- Engineers MUST NEVER trust bound closure parameters (e.g., `updateUserRole.bind(null, userId, 'ADMIN')`) as authoritative on the server side without cryptographic sealing or re-authorization against the authenticated session.
- Engineers MUST sign bound parameters with an HMAC (HMAC-SHA256) containing an expiration timestamp and active session ID whenever bound state must survive client-side round-trips.
- Engineers MUST verify the HMAC signature and assert that the bound session identifier matches the currently authenticated caller before performing privileged mutations.
- Engineers MUST prefer passing opaque sealed tokens or minimal identifiers and resolving authorization state directly from server-side session stores inside the action rather than binding business-critical state.
- Services MUST reject RPC invocations with expired timestamps, invalid HMAC signatures, or mismatched tenant/user contexts with a security violation exception.

## Bad vs Good Implementations
### Insecure Bound Arguments vs. Cryptographically Sealed Bound State

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: When React 19 binds arguments via `.bind()`, the arguments are serialized into the client payload. Attackers can intercept or synthesize the POST RPC request and alter the bound `targetRole` parameter from `VIEWER` to `ADMIN`.
```typescript
'use server';

import { db } from '@/lib/db';
import { getCurrentSession } from '@/lib/auth';

// VULNERABLE: Attackers can modify serialized bound arguments in transit via modified RPC payload
export async function updateResourcePrivilege(resourceId: string, targetRole: 'VIEWER' | 'ADMIN') {
  const session = await getCurrentSession();
  if (!session) throw new Error('Unauthorized');

  // Blindly trusts targetRole passed via .bind(null, resourceId, 'ADMIN')
  await db.resourcePermission.upsert({
    where: { resourceId_userId: { resourceId, userId: session.userId } },
    update: { role: targetRole },
    create: { resourceId, userId: session.userId, role: targetRole },
  });
}
```

#### Production Standard (Correct)
> **Standard**: The good example seals the bound parameters into a cryptographically signed HMAC token containing expiration and user context. Any tampering causes `timingSafeEqual` to fail, and replay by unauthorized users is prevented.
```typescript
'use server';

import { createHmac, timingSafeEqual } from 'node:crypto';
import { db } from '@/lib/db';
import { getCurrentSession } from '@/lib/auth';

const HMAC_SECRET = process.env.BOUND_STATE_SECRET!;

interface BoundPayload {
  resourceId: string;
  targetRole: 'VIEWER' | 'ADMIN';
  userId: string;
  expiresAt: number;
}

export function sealActionState(payload: Omit<BoundPayload, 'expiresAt'>): string {
  const data: BoundPayload = { ...payload, expiresAt: Date.now() + 15 * 60 * 1000 };
  const serialized = JSON.stringify(data);
  const signature = createHmac('sha256', HMAC_SECRET).update(serialized).digest('hex');
  return Buffer.from(JSON.stringify({ serialized, signature })).toString('base64url');
}

export async function updateResourcePrivilege(sealedToken: string) {
  const session = await getCurrentSession();
  if (!session) throw new Error('Unauthorized');

  const raw = Buffer.from(sealedToken, 'base64url').toString('utf8');
  const { serialized, signature } = JSON.parse(raw);

  const expectedSig = createHmac('sha256', HMAC_SECRET).update(serialized).digest('hex');
  const isValid = timingSafeEqual(Buffer.from(signature, 'hex'), Buffer.from(expectedSig, 'hex'));
  if (!isValid) throw new Error('HMAC signature verification failed: tampered state');

  const payload: BoundPayload = JSON.parse(serialized);
  if (Date.now() > payload.expiresAt) throw new Error('Action state expired');
  if (payload.userId !== session.userId) throw new Error('Identity mismatch in action token');

  await db.resourcePermission.upsert({
    where: { resourceId_userId: { resourceId: payload.resourceId, userId: session.userId } },
    update: { role: payload.targetRole },
    create: { resourceId: payload.resourceId, userId: session.userId, role: payload.targetRole },
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

fetch
Validates network payloads and inspects live HTTP RPC requests between React client and server boundaries.
Recommended Agent Skills (askills.dev)

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

Semgrep Static Analysis
Executes static AST rules detecting unverified arguments in 'use server' boundary functions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Actions Bound Closure State HMAC Sealing & Verification Invariant

React 19 Server Actions Bound Closure State HMAC Sealing & Verification Invariant defines an industrial-grade behavioral standard for frontend engineering. Guarantees that arguments bound to React 19 Server Actions via `.bind()` or closure capture cannot be tampered with or replayed across client-server RPC transitions. Any mutable or privileged bound parameters transmitted across the network boundary must be cryptographically signed with an HMAC token and verified against the authenticated session context before execution. 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: Trusting Client-Supplied Bound Arguments in Server Actions Without Cryptographic Integrity Verification 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 DriftTrusting Client-Supplied Bound Arguments in Server Actions Without Cryptographic Integrity VerificationCritical
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 NEVER trust bound closure parameters (e.g., `updateUserRole.bind(null, userId, 'ADMIN')`) as authoritative on the server side without cryptographic sealing or re-authorization against the authenticated session.

Engineers MUST NEVER trust bound closure parameters (e.g., `updateUserRole.bind(null, userId, 'ADMIN')`) as authoritative on the server side without cryptographic sealing or re-authorization against the authenticated session.

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 sign bound parameters with an HMAC (HMAC-SHA256) containing an expiration timestamp and active session ID whenever bound state must survive client-side round-trips.

Engineers MUST sign bound parameters with an HMAC (HMAC-SHA256) containing an expiration timestamp and active session ID whenever bound state must survive client-side round-trips.

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 verify the HMAC signature and assert that the bound session identifier matches the currently authenticated caller before performing privileged mutations.

Engineers MUST verify the HMAC signature and assert that the bound session identifier matches the currently authenticated caller before performing privileged 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.
4

Engineers MUST prefer passing opaque sealed tokens or minimal identifiers and resolving authorization state directly from server-side session stores inside the action rather than binding business-critical state.

Engineers MUST prefer passing opaque sealed tokens or minimal identifiers and resolving authorization state directly from server-side session stores inside the action rather than binding business-critical state.

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 reject RPC invocations with expired timestamps, invalid HMAC signatures, or mismatched tenant/user contexts with a security violation exception.

Services MUST reject RPC invocations with expired timestamps, invalid HMAC signatures, or mismatched tenant/user contexts with a security violation exception.

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 Actions Bound Closure State HMAC Sealing & Verification Invariant critical for AI coding assistants?

Guarantees that arguments bound to React 19 Server Actions via `.bind()` or closure capture cannot be tampered with or replayed across client-server RPC transitions. Any mutable or privileged bound parameters transmitted across the network boundary must be cryptographically signed with an HMAC token and verified against the authenticated session context before execution. 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 (Trusting Client-Supplied Bound Arguments in Server Actions Without Cryptographic Integrity Verification) 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