AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
securitycritical PriorityID: openfga-contextual-tuple-batch-isolation-boundary

OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail

Enforces strict request-scoped isolation and deterministic boundary checks when injecting contextual tuples into OpenFGA v1.8 runtime evaluation calls. Prevents cross-tenant authorization state leakage across concurrent batch evaluations and halts Denial-of-Service vectors stemming from unbounded graph traversals or recursive ephemeral relation cycles.

Prohibited Anti-Pattern: Leaking Ephemeral Contextual Tuples Across Concurrent Requests and Unbounded Zanzibar Graph Expansion

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail - Enforces strict request-scoped isolation and deterministic boundary checks when injecting contextual tuples into OpenFGA v1.8 runtime evaluation calls. Prevents cross-tenant authorization state leakage across concurrent batch evaluations and halts Denial-of-Service vectors stemming from unbounded graph traversals or recursive ephemeral relation cycles.
globs: src/**/authz/**/*.{ts,js,go}, src/**/permissions/**/*.{ts,js,go}, src/**/security/**/*.{ts,js,go}, src/**/services/**/*.{ts,js,go}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/openfga-contextual-tuple-batch-isolation-boundary"
---

# OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Leaking Ephemeral Contextual Tuples Across Concurrent Requests and Unbounded Zanzibar Graph Expansion

## System Constraints
You are a Principal Security Architect enforcing OpenFGA 1.8 Contextual Tuple Batch Evaluation Boundaries. In Zanzibar-based ReBAC architectures, contextual tuples injected during runtime Check or BatchCheck API calls alter the authorization graph ephemerally for the lifetime of that query. You must mandate strict tenant isolation, immutable per-request contexts, maximum cardinality constraints, and acyclic relation validation to eliminate cross-tenant contamination and traversal resource exhaustion.

## Strict Guidelines
- Engineers MUST ALWAYS construct contextual tuples (`contextual_tuples.tuple_keys`) as fresh, immutable, request-scoped data structures that are discarded immediately after evaluation.
- Engineers MUST NOT cache, mutate, or share contextual tuple arrays across concurrent promises, goroutines, batch workers, or tenant evaluation lifecycles.
- Services MUST validate that all object and user identifiers within contextual tuples match the ambient request's authenticated tenant partition (e.g., `tenant:<id>#...`) prior to dispatching queries to the OpenFGA store.
- Components NEVER accept unbounded external input as contextual tuples; systems MUST enforce a hard maximum cardinality limit (e.g., maximum 20 contextual tuples per batch check request) to prevent graph-traversal exhaustion attacks.
- Code SHOULD sanitize contextual tuple relations against recursive cycle definitions (e.g., parent-child or group-nesting cycles) before submission when derived from untrusted client-supplied claims.
- Services MUST explicitly pass an isolated evaluation context with strict timeout deadlines (e.g., <= 250ms) to abort runaway graph resolution in deep transitive relationship hierarchies.

## Bad vs Good Implementations
### Contextual Tuple Batch Evaluation Boundary

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The bad example utilizes a module-scoped mutable array (`sharedContextualTuples`) across asynchronous requests, causing concurrent evaluations from different tenants to evaluate against each other's ephemeral authorization state. It also fails to enforce tenant boundary checks, timeout deadlines, and tuple cardinality limits.
```typescript
import { OpenFgaClient, ClientBatchCheckRequest } from '@openfga/sdk';

// ANTI-PATTERN: Shared mutable batch context leaking cross-tenant ephemeral state
const sharedContextualTuples: Array<{ user: string; relation: string; object: string }> = [];

export async function authorizeBatchAccess(
  fgaClient: OpenFgaClient,
  tenantId: string,
  userId: string,
  resourceIds: string[],
  ephemeralRole?: string
) {
  // Flaw 1: Mutating shared state across concurrent execution paths
  if (ephemeralRole) {
    sharedContextualTuples.push({
      user: `user:${userId}`,
      relation: ephemeralRole,
      object: `tenant:${tenantId}`,
    });
  }

  // Flaw 2: No tenant isolation boundary validation on contextual tuples
  // Flaw 3: Unbounded batch check with no timeout context or tuple limit
  const checks: ClientBatchCheckRequest = resourceIds.map((resourceId) => ({
    user: `user:${userId}`,
    relation: 'viewer',
    object: `document:${resourceId}`,
    contextualTuples: sharedContextualTuples,
  }));

  return await fgaClient.batchCheck(checks);
}
```

#### Production Standard (Correct)
> **Standard**: The fixed implementation encapsulates contextual tuples within the local execution scope, enforces strict tenant namespace prefixing, validates tuple cardinality, and freezes request payloads. It executes evaluations with an explicit `AbortSignal.timeout` to prevent unbounded relational graph traversals.
```typescript
import { OpenFgaClient, ClientCheckRequest } from '@openfga/sdk';

const MAX_ALLOWED_CONTEXTUAL_TUPLES = 10;
const EVALUATION_TIMEOUT_MS = 250;

interface AuthorizationContext {
  tenantId: string;
  userId: string;
  resourceIds: string[];
  ephemeralRole?: 'viewer' | 'editor';
}

export async function authorizeBatchAccess(
  fgaClient: OpenFgaClient,
  context: Readonly<AuthorizationContext>
): Promise<Map<string, boolean>> {
  const { tenantId, userId, resourceIds, ephemeralRole } = context;

  // 1. Enforce strict ephemeral tuple scoping per execution context
  const contextualTuples: Array<{ user: string; relation: string; object: string }> = [];

  if (ephemeralRole) {
    // 2. Strict tenant prefixing and boundary validation
    const subject = `user:${tenantId}_${userId}`;
    const target = `tenant:${tenantId}`;

    contextualTuples.push(Object.freeze({
      user: subject,
      relation: ephemeralRole,
      object: target,
    }));
  }

  if (contextualTuples.length > MAX_ALLOWED_CONTEXTUAL_TUPLES) {
    throw new Error('SecurityException: Contextual tuple cardinality limit exceeded');
  }

  // 3. Isolated, immutable request mapping
  const checks: ClientCheckRequest[] = resourceIds.map((resourceId) => {
    // Ensure target resource strictly belongs to the executing tenant
    const objectId = `document:${tenantId}_${resourceId}`;
    return Object.freeze({
      user: `user:${tenantId}_${userId}`,
      relation: 'viewer',
      object: objectId,
      contextualTuples: [...contextualTuples],
    });
  });

  // 4. Bounded evaluation with explicit timeout
  const checkPromises = checks.map((req) =>
    fgaClient.check(req, {
      signal: AbortSignal.timeout(EVALUATION_TIMEOUT_MS),
    })
  );

  const results = await Promise.all(checkPromises);
  const resultMap = new Map<string, boolean>();

  resourceIds.forEach((id, index) => {
    resultMap.set(id, Boolean(results[index]?.allowed));
  });

  return resultMap;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

OpenFGA Schema and Model Validator MCP
Validates OpenFGA authorization models, relation cycles, and contextual tuple schemas during development.
Recommended Agent Skills (askills.dev)

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

OpenFGA Command Line Interface
CLI tool for testing stores, models, and running automated tuple batch assertions against Zanzibar rule boundaries.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail

OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail defines an industrial-grade behavioral standard for security engineering. Enforces strict request-scoped isolation and deterministic boundary checks when injecting contextual tuples into OpenFGA v1.8 runtime evaluation calls. Prevents cross-tenant authorization state leakage across concurrent batch evaluations and halts Denial-of-Service vectors stemming from unbounded graph traversals or recursive ephemeral relation cycles. 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: Leaking Ephemeral Contextual Tuples Across Concurrent Requests and Unbounded Zanzibar Graph Expansion 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 DriftLeaking Ephemeral Contextual Tuples Across Concurrent Requests and Unbounded Zanzibar Graph ExpansionCritical
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 construct contextual tuples (`contextual_tuples.tuple_keys`) as fresh, immutable, request-scoped data structures that are discarded immediately after evaluation.

Engineers MUST ALWAYS construct contextual tuples (`contextual_tuples.tuple_keys`) as fresh, immutable, request-scoped data structures that are discarded immediately after evaluation.

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 cache, mutate, or share contextual tuple arrays across concurrent promises, goroutines, batch workers, or tenant evaluation lifecycles.

Engineers MUST NOT cache, mutate, or share contextual tuple arrays across concurrent promises, goroutines, batch workers, or tenant evaluation lifecycles.

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

Services MUST validate that all object and user identifiers within contextual tuples match the ambient request's authenticated tenant partition (e.g., `tenant

Services MUST validate that all object and user identifiers within contextual tuples match the ambient request's authenticated tenant partition (e.g., `tenant:<id>#...`) prior to dispatching queries to the OpenFGA store.

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

Components NEVER accept unbounded external input as contextual tuples

Components NEVER accept unbounded external input as contextual tuples; systems MUST enforce a hard maximum cardinality limit (e.g., maximum 20 contextual tuples per batch check request) to prevent graph-traversal exhaustion attacks.

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 sanitize contextual tuple relations against recursive cycle definitions (e.g., parent-child or group-nesting cycles) before submission when derived from untrusted client-supplied claims.

Code SHOULD sanitize contextual tuple relations against recursive cycle definitions (e.g., parent-child or group-nesting cycles) before submission when derived from untrusted client-supplied claims.

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 explicitly pass an isolated evaluation context with strict timeout deadlines (e.g., <= 250ms) to abort runaway graph resolution in deep transitive relationship hierarchies.

Services MUST explicitly pass an isolated evaluation context with strict timeout deadlines (e.g., <= 250ms) to abort runaway graph resolution in deep transitive relationship hierarchies.

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 OpenFGA 1.8 Contextual Tuple Batch Isolation and Graph Depth Guardrail critical for AI coding assistants?

Enforces strict request-scoped isolation and deterministic boundary checks when injecting contextual tuples into OpenFGA v1.8 runtime evaluation calls. Prevents cross-tenant authorization state leakage across concurrent batch evaluations and halts Denial-of-Service vectors stemming from unbounded graph traversals or recursive ephemeral relation cycles. 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 (Leaking Ephemeral Contextual Tuples Across Concurrent Requests and Unbounded Zanzibar Graph Expansion) 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 SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

OpenFGA