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: tauri-v2-mobile-ipc-capability-isolation

Tauri 2.0 Mobile IPC Webview-Scoped Capability Isolation

Enforces strict zero-trust principle of least privilege for Tauri 2.0 Inter-Process Communication (IPC) on iOS and Android. Rejects global, wildcard, and ambient permission assignments by mandating deterministic, window-scoped capability files in src-tauri/capabilities/ with explicit remote origin validations and granular command mappings.

Prohibited Anti-Pattern: Ambient Core IPC Commands and Wildcard Permissions Assigned to Mobile Webviews

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Mobile IPC Webview-Scoped Capability Isolation - Enforces strict zero-trust principle of least privilege for Tauri 2.0 Inter-Process Communication (IPC) on iOS and Android. Rejects global, wildcard, and ambient permission assignments by mandating deterministic, window-scoped capability files in src-tauri/capabilities/ with explicit remote origin validations and granular command mappings.
globs: src-tauri/capabilities/**/*.json, src-tauri/src/main.rs, src-tauri/src/lib.rs, src-tauri/tauri.conf.json, src/**/*.{ts,tsx,js,jsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri-v2-mobile-ipc-capability-isolation"
---

# Tauri 2.0 Mobile IPC Webview-Scoped Capability Isolation

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Ambient Core IPC Commands and Wildcard Permissions Assigned to Mobile Webviews

## System Constraints
You are a Principal Security Architect enforcing Tauri 2.0 Mobile IPC Capability-Based Isolation. Mobile runtimes (iOS/Android) execute untrusted rendering engines with distinct threat profiles compared to desktop sandboxes. Mandate that all invoke() handlers and core plugins are strictly gated behind isolated capability manifests with zero ambient access.

## Strict Guidelines
- Engineers MUST ALWAYS isolate mobile capabilities into dedicated files under `src-tauri/capabilities/` targeting specific webview window labels (e.g., `main`, `auth-modal`).
- Engineers MUST NOT grant catch-all core permissions (e.g., `core:default`, `fs:allow-all`) within mobile platform capability files.
- Engineers MUST explicitly constrain `platforms` to `["iOS", "android"]` when configuring mobile-specific IPC permissions.
- Engineers MUST validate remote URLs using strict domain and path matching rules in `remote` contexts if loading remote content into a mobile webview.
- Code SHOULD wrap all frontend `@tauri-apps/api/core` `invoke()` calls in strongly-typed, runtime-validated transport boundaries that handle mobile IPC security denials cleanly.

## Bad vs Good Implementations
### Configuring Secure Scoped Capability vs Ambient Wildcard Access

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Assigning wildcard windows (`"*"`) and default permissive plugin sets (`core:default`, `fs:default`, `shell:default`) breaks zero-trust isolation on mobile, exposing native device access to any navigated or injected script.
```json
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "mobile-capabilities",
  "description": "Insecure ambient mobile permissions",
  "windows": ["*"],
  "permissions": [
    "core:default",
    "fs:default",
    "shell:default"
  ]
}
```

#### Production Standard (Correct)
> **Standard**: Binds specific, granular permissions to the explicit window label (`main`) on verified platforms (`iOS`, `android`), restricting file system read operations solely to the `$APPDATA` directory hierarchy.
```json
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "mobile-primary-webview-capability",
  "description": "Least-privilege scoped permissions for main mobile webview",
  "windows": ["main"],
  "platforms": ["iOS", "android"],
  "permissions": [
    "core:path:allow-app-cache-dir",
    "core:path:allow-app-data-dir",
    "core:event:allow-listen",
    {
      "identifier": "fs:allow-read-file",
      "allow": [{
        "path": "$APPDATA/**"
      }]
    }
  ]
}
```

### Safe IPC Frontend Invocation with Fallback Handling

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Lacks schema validation and unhandled IPC security errors will crash or stall mobile UI flows without actionable diagnostics when capabilities reject the command.
```typescript
import { invoke } from '@tauri-apps/api/core';

export async function loadUserData(userId: string) {
  // Dangerous: Unchecked native call directly assumes unlimited ambient IPC
  return await invoke('load_secure_user_record', { userId });
}
```

#### Production Standard (Correct)
> **Standard**: Targets a scoped plugin command endpoint, strictly defines return structures, and provides defensive error boundary handling when mobile capability constraints deny execution.
```typescript
import { invoke } from '@tauri-apps/api/core';

export interface SecureUserRecord {
  readonly id: string;
  readonly email: string;
}

export async function loadUserData(userId: string): Promise<SecureUserRecord | null> {
  try {
    return await invoke<SecureUserRecord>('plugin:app-store|load_secure_user_record', {
      payload: { userId }
    });
  } catch (error: unknown) {
    const message = error instanceof Error ? error.message : String(error);
    console.error(`[IPC Mobile Boundary Security Fault]: ${message}`);
    return null;
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri CLI Inspector MCP
Validates Tauri 2.0 configuration, capability JSON schemas, and platform compilation flags.
Recommended Agent Skills (askills.dev)

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

Tauri Capability Auditor
CLI utility to lint and dry-run Tauri 2.0 ACLs and capability mappings against target mobile webviews.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Mobile IPC Webview-Scoped Capability Isolation

Tauri 2.0 Mobile IPC Webview-Scoped Capability Isolation defines an industrial-grade behavioral standard for mobile engineering. Enforces strict zero-trust principle of least privilege for Tauri 2.0 Inter-Process Communication (IPC) on iOS and Android. Rejects global, wildcard, and ambient permission assignments by mandating deterministic, window-scoped capability files in src-tauri/capabilities/ with explicit remote origin validations and granular command mappings. 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: Ambient Core IPC Commands and Wildcard Permissions Assigned to Mobile Webviews 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 DriftAmbient Core IPC Commands and Wildcard Permissions Assigned to Mobile WebviewsCritical
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 isolate mobile capabilities into dedicated files under `src-tauri/capabilities/` targeting specific webview window labels (e.g., `main`, `auth-modal`).

Engineers MUST ALWAYS isolate mobile capabilities into dedicated files under `src-tauri/capabilities/` targeting specific webview window labels (e.g., `main`, `auth-modal`).

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 catch-all core permissions (e.g., `core

Engineers MUST NOT grant catch-all core permissions (e.g., `core:default`, `fs:allow-all`) within mobile platform capability files.

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 explicitly constrain `platforms` to `["iOS", "android"]` when configuring mobile-specific IPC permissions.

Engineers MUST explicitly constrain `platforms` to `["iOS", "android"]` when configuring mobile-specific IPC permissions.

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 validate remote URLs using strict domain and path matching rules in `remote` contexts if loading remote content into a mobile webview.

Engineers MUST validate remote URLs using strict domain and path matching rules in `remote` contexts if loading remote content into a mobile webview.

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 wrap all frontend `@tauri-apps/api/core` `invoke()` calls in strongly-typed, runtime-validated transport boundaries that handle mobile IPC security denials cleanly.

Code SHOULD wrap all frontend `@tauri-apps/api/core` `invoke()` calls in strongly-typed, runtime-validated transport boundaries that handle mobile IPC security denials cleanly.

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 Mobile IPC Webview-Scoped Capability Isolation critical for AI coding assistants?

Enforces strict zero-trust principle of least privilege for Tauri 2.0 Inter-Process Communication (IPC) on iOS and Android. Rejects global, wildcard, and ambient permission assignments by mandating deterministic, window-scoped capability files in src-tauri/capabilities/ with explicit remote origin validations and granular command mappings. 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 (Ambient Core IPC Commands and Wildcard Permissions Assigned to Mobile Webviews) 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