AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
mobilecritical PriorityID: tauri2-ipc-zero-trust-capability-scoping-guardrail

Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail

Enforces strict principle-of-least-privilege access control list (ACL) definitions and granular capability scoping in Tauri 2.0 applications. Prohibits wildcard permissions, unbounded filesystem access, and untyped dynamic IPC invokers across mobile webview-to-Rust native execution boundaries.

Prohibited Anti-Pattern: Over-privileged IPC Surface via Wildcard Capabilities and Arbitrary Native Command Invocation

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail - Enforces strict principle-of-least-privilege access control list (ACL) definitions and granular capability scoping in Tauri 2.0 applications. Prohibits wildcard permissions, unbounded filesystem access, and untyped dynamic IPC invokers across mobile webview-to-Rust native execution boundaries.
globs: src-tauri/capabilities/**/*.json, src-tauri/src/**/*.rs, src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri2-ipc-zero-trust-capability-scoping-guardrail"
---

# Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Over-privileged IPC Surface via Wildcard Capabilities and Arbitrary Native Command Invocation

## System Constraints
You are a Principal Security Architect enforcing the Tauri 2.0 IPC Zero-Trust Capability Scoping Guardrail. Tauri 2.0 eliminates legacy allowlists in favor of capability files, permission sets, and webview window associations. You must ensure all IPC calls and native capabilities adhere to absolute least-privilege scoping, rigorous schema validation at the Rust-webview boundary, and zero reliance on wildcard privileges or unauthenticated invocations.

## Strict Guidelines
- Engineers MUST ALWAYS declare granular capability JSON files under `src-tauri/capabilities/` targeting specific window labels rather than using universal wildcards (`*`).
- Engineers MUST NOT grant broad plugin permissions (e.g., `fs:default`, `shell:allow-execute`) without strict scoping constraints (`scope: [{ path: ... }]`).
- Engineers MUST ALWAYS validate IPC arguments on both the TypeScript frontend (via Zod or ArkType) and the native Rust runtime (via Serde deserialization and explicit domain checks) before dispatching business logic.
- Native commands exposed via `#[tauri::command]` MUST validate execution context, window identifiers, and session tokens prior to mutating system state or reading device credentials.
- Components NEVER invoke raw, unstructured strings via `invoke()` without compile-time contract definitions linking frontend payloads directly to Rust IPC return signatures.

## Bad vs Good Implementations
### Tauri 2.0 Capability Declaration: Wildcard Over-Privilege vs Scoped Least-Privilege

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Assigning permissions to `"windows": ["*"]` exposes the capability to rogue or compromised webviews/iframes. Specifying `fs:allow-read` without a `scope` block grants unconstrained read access to the entire mobile host filesystem.
```typescript
// src-tauri/capabilities/mobile-capabilities.json (Overly permissive anti-pattern)
// {
//   "$schema": "../gen/schemas/desktop-schema.json",
//   "identifier": "mobile-default",
//   "description": "Broad permissions for mobile app",
//   "windows": ["*"],
//   "permissions": [
//     "core:default",
//     "fs:allow-read",
//     "fs:allow-write"
//   ]
// }

import { invoke } from '@tauri-apps/api/core';

export async function readDeviceFile(path: string) {
  // Anti-Pattern: Unvalidated frontend pass-through to unconstrained native filesystem
  return await invoke('plugin:fs|read_text_file', { path });
}
```

#### Production Standard (Correct)
> **Standard**: Limits access exclusively to the 'main' window target, constrains the filesystem plugin permission to `$APPDATA/documents/*` using Tauri 2.0 ACL scoping, and validates the input using Zod before invoking the IPC boundary.
```typescript
// src-tauri/capabilities/mobile-secure.json
// {
//   "$schema": "../gen/schemas/desktop-schema.json",
//   "identifier": "mobile-secure-docs",
//   "description": "Scoped access to app documents directory only",
//   "windows": ["main"],
//   "permissions": [
//     "core:default",
//     {
//       "identifier": "fs:allow-read-text-file",
//       "allow": [{ "path": "$APPDATA/documents/*" }]
//     }
//   ]
// }

import { invoke } from '@tauri-apps/api/core';
import { z } from 'zod';

const SafePathSchema = z.string().regex(/^[a-zA-Z0-9_-]+\.json$/);

export async function readSecureDocument(fileName: string): Promise<string> {
  const validated = SafePathSchema.parse(fileName);
  const fullPath = `$APPDATA/documents/${validated}`;
  return await invoke<string>('plugin:fs|read_text_file', { path: fullPath });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri Security Audit MCP
Analyzes Tauri 2.0 capability definitions, permission sets, and IPC bindings for least-privilege compliance.
Recommended Agent Skills (askills.dev)

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

Tauri CLI Capability Validator
Runs `cargo tauri capability` and static security checks against target capability configurations.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail

Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail defines an industrial-grade behavioral standard for mobile engineering. Enforces strict principle-of-least-privilege access control list (ACL) definitions and granular capability scoping in Tauri 2.0 applications. Prohibits wildcard permissions, unbounded filesystem access, and untyped dynamic IPC invokers across mobile webview-to-Rust native execution boundaries. 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: Over-privileged IPC Surface via Wildcard Capabilities and Arbitrary Native Command Invocation 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 DriftOver-privileged IPC Surface via Wildcard Capabilities and Arbitrary Native Command InvocationCritical
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 declare granular capability JSON files under `src-tauri/capabilities/` targeting specific window labels rather than using universal wildcards (`*`).

Engineers MUST ALWAYS declare granular capability JSON files under `src-tauri/capabilities/` targeting specific window labels rather than using universal wildcards (`*`).

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 grant broad plugin permissions (e.g., `fs

Engineers MUST NOT grant broad plugin permissions (e.g., `fs:default`, `shell:allow-execute`) without strict scoping constraints (`scope: [{ path: ... }]`).

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 validate IPC arguments on both the TypeScript frontend (via Zod or ArkType) and the native Rust runtime (via Serde deserialization and explicit domain checks) before dispatching business logic.

Engineers MUST ALWAYS validate IPC arguments on both the TypeScript frontend (via Zod or ArkType) and the native Rust runtime (via Serde deserialization and explicit domain checks) before dispatching business logic.

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

Native commands exposed via `#[tauri

Native commands exposed via `#[tauri::command]` MUST validate execution context, window identifiers, and session tokens prior to mutating system state or reading device credentials.

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 invoke raw, unstructured strings via `invoke()` without compile-time contract definitions linking frontend payloads directly to Rust IPC return signatures.

Components NEVER invoke raw, unstructured strings via `invoke()` without compile-time contract definitions linking frontend payloads directly to Rust IPC return signatures.

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 Tauri 2.0 Zero-Trust IPC Capability Scoping and Granular ACL Guardrail critical for AI coding assistants?

Enforces strict principle-of-least-privilege access control list (ACL) definitions and granular capability scoping in Tauri 2.0 applications. Prohibits wildcard permissions, unbounded filesystem access, and untyped dynamic IPC invokers across mobile webview-to-Rust native execution boundaries. 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 (Over-privileged IPC Surface via Wildcard Capabilities and Arbitrary Native Command Invocation) 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 MOBILE Rules

View all rules →
mobile
106

Tauri 2.0 Mobile IPC & Capabilities Permissions Matrix Standard

Tauri v2 introduces a capability-driven permissions system replacing legacy v1 allowlists across iOS and Android runtimes. Failure to constrain IPC command handlers with typed schemas and explicit mobile capability definitions exposes native mobile OS surfaces to arbitrary code execution, permission leakage, and silent serialization failures. Production mobile deployments require strictly typed IPC boundary validation, granular capability scopes, and graceful permission degradation.

mobile
70

Capacitor 7 Native Bridge, Biometric Auth & Android 15 Lifecycle Production Standard

Capacitor 7 enforces strict bridge lifecycle contracts, asynchronous native plugin interop, and mandatory Android 15 edge-to-edge window inset handling. Storing sensitive authentication tokens in unencrypted web storage or failing to bind biometric authentication directly to hardware-backed Keystore or Secure Enclave mechanisms compromises app integrity and causes fatal crash or viewport occlusion issues on modern mobile operating systems.

mobile
58

Tauri 2.0 Mobile IPC Isolation and Capabilities Permission Scoping

Enforces strict capability permission boundaries, payload validation, and secure IPC invoke scoping for Tauri v2 Android and iOS environments. Prevents arbitrary IPC command execution, excessive native privilege granting, and deserialization vulnerabilities across the mobile webview-native boundary.

1 Rule in Stack

Tauri