Tauri 2.0 Mobile IPC Permission Scoping and Multi-Webview Isolation

--- description: Tauri 2.0 Mobile IPC Permission Scoping and Multi-Webview Isolation - Enforces strict capability-based access control, granular IPC command allowlists, and origin isolation in Tauri 2.0 mobile applications. Prevents compromised third-party webview assets or remote webviews from escalating privileges into native Rust system APIs via unscoped wildcard permissions or unvalidated command invocations. globs: src-tauri/tauri.conf.json, src-tauri/capabilities/**/*.json, src-tauri/src/**/*.rs, src/**/*.{ts,tsx,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-ipc-permission-scoping-isolation" --- # Tauri 2.0 Mobile IPC Permission Scoping and Multi-Webview Isolation > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Wildcard IPC Capabilities and Unscoped Command Invocation Across Webview Contexts ## System Constraints You are a Principal Security Architect enforcing Tauri 2.0 IPC Permission Scoping and Isolation. Mandate invariants that eliminate supply-chain blast radiuses by decoupling frontend contexts from native core commands. Ensure all Rust commands define explicit permission capabilities, prevent wildcard command exports, restrict IPC invocations to verified local origins, and isolate webview contexts on mobile runtimes. ## Strict Guidelines - Engineers MUST ALWAYS declare fine-grained permissions in individual capability files under `src-tauri/capabilities/` and explicitly map each capability to exact window/webview labels. - Engineers MUST NOT grant wildcard permissions (`core:default`, `fs:default`, `shell:all`, or `*`) to any webview context, especially remote or secondary mobile webviews. - Engineers MUST validate the caller context in Rust commands using `tauri::ipc::Request` or `tauri::WebviewWindow` to verify origin and window identity before executing privileged native operations. - Services MUST isolate untrusted remote content into dedicated sandboxed webviews with all IPC bindings disabled (`core:event:allow-listen` and `invoke` explicitly denied). - Components NEVER execute raw dynamic string invocations via `invoke(dynamicVar, payload)`; all IPC invocations in frontend code MUST use compile-time type-checked wrappers generated from Rust command schemas. ## Bad vs Good Implementations ### Tauri 2.0 Capability Definition: Wildcard vs Scoped Permissions #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Assigning 'core:default' and 'fs:default' with wildcard window targets ('*') allows any injected dependency or hijacked webview to read, write, or execute arbitrary native operations across the mobile device. ```json { "$schema": "../gen/schemas/desktop-schema.json", "identifier": "mobile-capability", "description": "Insecure wildcard permissions for all windows", "windows": ["*"], "permissions": [ "core:default", "fs:default", "shell:allow-open" ] } ``` #### Production Standard (Correct) > **Standard**: Explicitly binds narrow permissions to only the 'main' window label and constrains file system access strictly to an application-scoped subdirectory using Tauri path variables. ```json { "$schema": "../gen/schemas/desktop-schema.json", "identifier": "mobile-main-capability", "description": "Scoped native access restricted strictly to the primary secure webview", "windows": ["main"], "permissions": [ "core:event:allow-emit", "core:event:allow-listen", { "identifier": "fs:allow-read-text-file", "allow": [{ "path": "$APPDATA/secure_storage/*" }] } ] } ``` ### Rust Command Isolation: Unchecked Execution vs Identity-Guarded Handler #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Fails to inspect the calling webview origin or window label, exposing sensitive cryptographic secrets to any compromised webview frame or injected script. ```rust // Unchecked command allowing any webview to trigger sensitive native tasks #[tauri::command] pub async fn read_secure_vault(key_id: String) -> Result<String, String> { vault::retrieve_secret(&key_id).map_err(|e| e.to_string()) } ``` #### Production Standard (Correct) > **Standard**: Validates the calling WebviewWindow context directly in the command handler and strictly verifies that only the designated 'main' webview can access sensitive key material. ```rust use tauri::{command, AppHandle, Runtime, WebviewWindow}; #[command] pub async fn read_secure_vault<R: Runtime>( window: WebviewWindow<R>, key_id: String, ) -> Result<String, String> { // Invariant: Only verified local 'main' webview may query sensitive vault items if window.label() != "main" { return Err("Unauthorized caller context: IPC invocation denied".into()); } // Validate input payload to prevent injection if !key_id.chars().all(|c| c.is_ascii_alphanumeric() || c == '_') { return Err("Invalid key_id format".into()); } vault::retrieve_secret(&key_id).map_err(|e| e.to_string()) } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Mobile IPC Permission Scoping and Multi-Webview Isolation

Tauri 2.0 Mobile IPC Permission Scoping and Multi-Webview Isolation defines an industrial-grade behavioral standard for mobile engineering. Enforces strict capability-based access control, granular IPC command allowlists, and origin isolation in Tauri 2.0 mobile applications. Prevents compromised third-party webview assets or remote webviews from escalating privileges into native Rust system APIs via unscoped wildcard permissions or unvalidated command invocations. 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: Wildcard IPC Capabilities and Unscoped Command Invocation Across Webview Contexts 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Wildcard IPC Capabilities and Unscoped Command Invocation Across Webview Contexts	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 Inconsistency	AI 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:

Engineers MUST ALWAYS declare fine-grained permissions in individual capability files under `src-tauri/capabilities/` and explicitly map each capability to exact window/webview labels.

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.