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-granular-ipc-capability-scoping-tauri-2-0-granul-582

Tauri 2.0 Granular IPC Capability and Origin Scoping

Tauri 2.0 introduces an Access Control List (ACL) security model for native Rust commands and core plugins. In mobile and embedded webview environments, engineers must explicitly define granular capability boundaries, strictly binding high-privilege native capabilities to validated local bundle origins while prohibiting wildcard permissions on arbitrary remote web contexts.

Prohibited Anti-Pattern: Assigning Default Wildcard Permissions and Unscoped Host Plugins to Webview Contexts

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Granular IPC Capability and Origin Scoping - Tauri 2.0 introduces an Access Control List (ACL) security model for native Rust commands and core plugins. In mobile and embedded webview environments, engineers must explicitly define granular capability boundaries, strictly binding high-privilege native capabilities to validated local bundle origins while prohibiting wildcard permissions on arbitrary remote web contexts.
globs: src-tauri/capabilities/**/*.json, src-tauri/tauri.conf.json, src/**/*.{ts,tsx}, src-tauri/src/**/*.rs
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri-v2-granular-ipc-capability-scoping-tauri-2-0-granul-582"
---

# Tauri 2.0 Granular IPC Capability and Origin Scoping

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Assigning Default Wildcard Permissions and Unscoped Host Plugins to Webview Contexts

## System Constraints
You are a Principal Security Architect enforcing Tauri 2.0 Granular IPC Capability Scoping on mobile and desktop platforms. Mandate least-privilege capability manifests, origin-bound webviews, and explicit command access validation. Prevent wildcard permission sets, arbitrary host execution, and unauthorized native plugin exposure to untrusted webview windows.

## Strict Guidelines
- Engineers MUST ALWAYS isolate native capabilities into explicit, context-specific JSON/TOML manifests inside `src-tauri/capabilities/` instead of granting universal global scopes.
- Engineers MUST NOT grant `core:default`, `shell:allow-execute`, or broad filesystem permissions to windows rendering external or unvalidated webview origins.
- Code SHOULD enforce strict path and argument scoping rules for all native plugins (such as `fs`, `http`, and `dialog`) within capability manifests.
- Services MUST restrict mobile webview access to bundle-internal schemas (e.g., `tauri://localhost` or native custom asset protocols) and cryptographically pinned remote origins.
- Components NEVER invoke unmapped custom invoke commands without verifying IPC permission mapping in the corresponding capability file.

## Bad vs Good Implementations
### Configuring Tauri 2.0 Granular Capability vs Wildcard Insecure Mapping

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Assigning `*` to window targets and granting `fs:default` or `shell:default` allows any loaded context (including injected scripts or rogue redirects on mobile webviews) to invoke dangerous native system APIs without origin validation.
```typescript
// src-tauri/capabilities/mobile.json (Anti-Pattern: Excessive permissions and open origin)
/*
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "mobile-capability",
  "windows": ["*"],
  "permissions": [
    "core:default",
    "fs:default",
    "shell:default"
  ]
}
*/

// src/services/nativeStorage.ts
import { invoke } from '@tauri-apps/api/core';

export async function writeSensitiveToken(token: string): Promise<void> {
  // Insecure: invoking unconstrained host command accessible to any injected script
  await invoke('save_auth_token', { token });
}
```

#### Production Standard (Correct)
> **Standard**: The capability manifest targets only the trusted 'main' window, disallows wildcard filesystem and shell execution, and constrains native plugin invocations to strictly designated paths and command identifiers.
```typescript
// src-tauri/capabilities/mobile-auth.json (Production standard: Granular & Window-Bound)
/*
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "mobile-auth-capability",
  "description": "Restricts secure token persistence strictly to the authenticated main window.",
  "windows": ["main"],
  "permissions": [
    "core:event:default",
    {
      "identifier": "fs:allow-write-text-file",
      "allow": [{ "path": "$APPDATA/secure/session.enc" }]
    }
  ]
}
*/

// src/services/nativeStorage.ts
import { invoke } from '@tauri-apps/api/core';

export async function writeSensitiveToken(token: string): Promise<void> {
  // Command explicitly bound to "main" window capability with enforced parameter validation
  await invoke('plugin:secure-storage|save_auth_token', { 
    payload: { token }
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri Documentation Server
MCP fetch service to query up-to-date Tauri 2.0 security ACL and permission schema definitions.
Recommended Agent Skills (askills.dev)

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

Cargo Tauri CLI
Command-line tool for auditing Tauri permission manifests and generating platform-specific capability schemas via `cargo tauri capability`.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Granular IPC Capability and Origin Scoping

Tauri 2.0 Granular IPC Capability and Origin Scoping defines an industrial-grade behavioral standard for mobile engineering. Tauri 2.0 introduces an Access Control List (ACL) security model for native Rust commands and core plugins. In mobile and embedded webview environments, engineers must explicitly define granular capability boundaries, strictly binding high-privilege native capabilities to validated local bundle origins while prohibiting wildcard permissions on arbitrary remote web contexts. 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: Assigning Default Wildcard Permissions and Unscoped Host Plugins to 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAssigning Default Wildcard Permissions and Unscoped Host Plugins to Webview ContextsCritical
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 native capabilities into explicit, context-specific JSON/TOML manifests inside `src-tauri/capabilities/` instead of granting universal global scopes.

Engineers MUST ALWAYS isolate native capabilities into explicit, context-specific JSON/TOML manifests inside `src-tauri/capabilities/` instead of granting universal global scopes.

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 `core

Engineers MUST NOT grant `core:default`, `shell:allow-execute`, or broad filesystem permissions to windows rendering external or unvalidated webview origins.

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

Code SHOULD enforce strict path and argument scoping rules for all native plugins (such as `fs`, `http`, and `dialog`) within capability manifests.

Code SHOULD enforce strict path and argument scoping rules for all native plugins (such as `fs`, `http`, and `dialog`) within capability manifests.

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

Services MUST restrict mobile webview access to bundle-internal schemas (e.g., `tauri

Services MUST restrict mobile webview access to bundle-internal schemas (e.g., `tauri://localhost` or native custom asset protocols) and cryptographically pinned remote origins.

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 unmapped custom invoke commands without verifying IPC permission mapping in the corresponding capability file.

Components NEVER invoke unmapped custom invoke commands without verifying IPC permission mapping in the corresponding capability file.

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 Granular IPC Capability and Origin Scoping critical for AI coding assistants?

Tauri 2.0 introduces an Access Control List (ACL) security model for native Rust commands and core plugins. In mobile and embedded webview environments, engineers must explicitly define granular capability boundaries, strictly binding high-privilege native capabilities to validated local bundle origins while prohibiting wildcard permissions on arbitrary remote web contexts. 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 (Assigning Default Wildcard Permissions and Unscoped Host Plugins to Webview Contexts) 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