Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid

--- description: Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid - Enforces strict compile-time Access Control List (ACL) manifests and fine-grained capability isolation for Tauri 2.0 mobile bridges. Prohibits global wildcards, unvalidated plugin identifiers, and ambient native API execution to prevent compromised webview contexts from invoking privileged device subsystems. globs: src-tauri/capabilities/**/*.json, src-tauri/tauri.conf.json, src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-mobile-ipc-capability-isolation-grid" --- # Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Wildcard Capability Manifests and Ambient IPC Bridges Exposing Native Mobile Hardware APIs ## System Constraints You are a Principal Security Architect enforcing the Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid. Mandate strict compile-time ACL capabilities, isolated webview window mappings, granular native permission scopes (e.g., biometric authentication, camera, filesystem), and cryptographically validated payload structures for all webview-to-native bridges. Reject any reliance on default-allow policies, wildcard permission scopes ('*:*'), or dynamic unvalidated invoke channels. ## Strict Guidelines - Engineers MUST ALWAYS isolate mobile capabilities into dedicated JSON manifest files under `src-tauri/capabilities/` scoped strictly to target webview window labels. - Engineers MUST NOT grant wildcard plugin permissions (such as `core:default` or `biometric:*`) in any capability manifest targeting mobile platforms. - Code MUST strictly define explicit allow/deny ACL sets for mobile plugin commands and specific argument schemas. - Services MUST gate native mobile invocation calls behind strongly typed client-side IPC wrappers that enforce local boundary schema validation before dispatch. - Components NEVER invoke raw `window.__TAURI_INTERNALS__.invoke` or uncurried `@tauri-apps/api/core::invoke` directly without an intermediary, typed, and permission-isolated service layer. ## Bad vs Good Implementations ### Tauri 2.0 Mobile Capability Isolation Manifest #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Assigning permissions to wildcard windows ('*') and applying blanket default/allow-all plugin permissions allows any untrusted route or injected script inside the webview to execute high-privilege mobile hardware interfaces without argument constraint. ```json { "$schema": "../gen/schemas/desktop-schema.json", "identifier": "mobile-capability", "description": "Insecure ambient mobile permissions", "windows": ["*"], "permissions": [ "core:default", "biometric:default", "camera:allow-all" ] } ``` #### Production Standard (Correct) > **Standard**: Limits capabilities strictly to the verified 'main' window label, defines precise operation identifiers, explicitly denies dangerous continuous background sweeps, and constrains execution parameters via declarative schema guards. ```json { "$schema": "../gen/schemas/desktop-schema.json", "identifier": "mobile-capability-isolated", "description": "Granular scoped mobile capabilities for the authenticated app webview", "windows": ["main"], "permissions": [ { "identifier": "biometric:authenticate", "allow": [ { "reason": "Verify user identity for transaction processing" } ] }, "camera:deny-camera-scan-continuous", { "identifier": "camera:allow-capture-frame", "allow": [ { "targetResolution": "1080p" } ] } ] } ``` ### Front-End Type-Safe Mobile IPC Wrapper with Boundary Validation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Directly passing untyped arguments via raw invoke strings bypasses client-side schema contracts and relies purely on native catch blocks, potentially exposing system state or crashing native bridge runtimes if malformed inputs reach IPC serialisers. ```typescript import { invoke } from '@tauri-apps/api/core'; // Unsafe: direct invocation with raw payload and no boundary assertions export async function captureBiometricAuth(reason: string): Promise<boolean> { return await invoke('plugin:biometric|authenticate', { reason }); } ``` #### Production Standard (Correct) > **Standard**: Implements an immutable type contract, enforces strict client-side validation rules prior to dispatching across the FFI/JNI bridge, and isolates the native plugin command call behind a dedicated application service boundary. ```typescript import { invoke } from '@tauri-apps/api/core'; interface BiometricAuthOptions { readonly reason: string; readonly timeoutMs?: number; } interface BiometricAuthResult { readonly success: boolean; readonly token?: string; } export async function captureBiometricAuth( options: BiometricAuthOptions ): Promise<BiometricAuthResult> { if (!options.reason || options.reason.length < 8) { throw new Error('IPC Precondition Failure: Biometric authentication reason must be explicitly detailed.'); } return await invoke<BiometricAuthResult>('plugin:biometric|authenticate', { payload: { reason: options.reason, timeoutMs: options.timeoutMs ?? 30000, }, }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid

Tauri 2.0 Mobile Plugin IPC Capability Isolation Grid defines an industrial-grade behavioral standard for mobile engineering. Enforces strict compile-time Access Control List (ACL) manifests and fine-grained capability isolation for Tauri 2.0 mobile bridges. Prohibits global wildcards, unvalidated plugin identifiers, and ambient native API execution to prevent compromised webview contexts from invoking privileged device subsystems. 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 Capability Manifests and Ambient IPC Bridges Exposing Native Mobile Hardware APIs 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 Capability Manifests and Ambient IPC Bridges Exposing Native Mobile Hardware APIs	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 isolate mobile capabilities into dedicated JSON manifest files under `src-tauri/capabilities/` scoped strictly to target webview window 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.