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-mobile-plugin-acl-permission-matrix-standard

Tauri 2.0 Mobile Plugin Scoped Capability & ACL Enforcement

Enforces granular compile-time capabilities and runtime ACL scoping for Tauri 2.0 iOS and Android plugin bridges. Prevents arbitrary IPC bridge privilege escalation by prohibiting un-scoped default plugin sets and wildcards across webview execution contexts.

Prohibited Anti-Pattern: Over-privileged IPC bridges granting broad runtime filesystem, biometric, or hardware access across mobile webview boundaries.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Mobile Plugin Scoped Capability & ACL Enforcement - Enforces granular compile-time capabilities and runtime ACL scoping for Tauri 2.0 iOS and Android plugin bridges. Prevents arbitrary IPC bridge privilege escalation by prohibiting un-scoped default plugin sets and wildcards across webview execution contexts.
globs: src/**/*.{ts,tsx}, src-tauri/capabilities/**/*.json, src-tauri/tauri.conf.json, src-tauri/src/**/*.rs
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri-mobile-plugin-acl-permission-matrix-standard"
---

# Tauri 2.0 Mobile Plugin Scoped Capability & ACL Enforcement

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Over-privileged IPC bridges granting broad runtime filesystem, biometric, or hardware access across mobile webview boundaries.

## System Constraints
You are a Principal Software Architect enforcing Tauri 2.0 mobile security invariants. In Tauri 2.0 mobile targets (iOS and Android), the native-to-webview IPC bridge is the primary attack surface. You must mandate compile-time capability isolation, platform-specific target boundaries, explicit command ACL lists, and strict filesystem/hardware scoping. Wildcard permissions (*), root directory access, and implicit default plugin grants are strictly forbidden.

## Strict Guidelines
- Engineers MUST ALWAYS declare isolated capabilities per window and mobile platform in `src-tauri/capabilities/*.json` instead of using root default configs.
- Engineers MUST NEVER use `*:default` or un-scoped capability sets (e.g., `fs:default` without a path scope array) in mobile deployment targets.
- Code MUST strictly scope plugin access to mobile sandbox directories (`$APPDATA`, `$RESOURCE`, `$CACHE`) using `BaseDirectory` enums rather than arbitrary string paths.
- Services MUST verify runtime permission status via plugin-specific `checkPermissions()` and `requestPermissions()` before dispatching IPC invocations on Android/iOS.
- Components NEVER invoke raw, untyped `invoke('plugin:...')` commands bypassing the compiled Tauri 2.0 mobile client SDK.

## Bad vs Good Implementations
### Tauri 2.0 Scoped Mobile File Access & Runtime Permission Check

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Directly invoking the raw fs plugin with arbitrary strings bypasses compile-time capability path restrictions, fails on mobile operating system sandbox constraints, and breaches Tauri 2.0 least-privilege IPC boundaries.
```typescript
import { invoke } from '@tauri-apps/api/core';

// CRITICAL FLAW: Untyped, un-scoped IPC execution attempting direct path access.
// This relies on an open/un-scoped capability and can trigger bridge privilege escalation.
export async function readMobileUserData(rawPath: string): Promise<Uint8Array> {
  return await invoke<Uint8Array>('plugin:fs|read_file', {
    path: rawPath,
  });
}
```

#### Production Standard (Correct)
> **Standard**: Restricts execution to the compiled capability path matrix using Tauri 2.0 BaseDirectory scoping, mitigating directory traversal attacks and adhering to mobile application sandbox boundaries.
```typescript
import { readFile, BaseDirectory } from '@tauri-apps/plugin-fs';

// PRODUCTION INVARIANT: Enforces BaseDirectory scoping aligned with
// Tauri 2.0 capability permissions (e.g. "fs:scope": [{ "path": "$APPDATA/secure/**" }])
export async function readMobileUserData(relativeFilename: string): Promise<Uint8Array> {
  if (relativeFilename.includes('..') || relativeFilename.startsWith('/')) {
    throw new Error('Directory traversal attempt detected');
  }

  return await readFile(relativeFilename, {
    baseDir: BaseDirectory.AppData,
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri v2 Documentation Server
Validates Tauri 2.0 capability definitions, permission syntax, and ACL schemas.
Recommended Agent Skills (askills.dev)

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

Tauri CLI Capability Validator
Runs cargo tauri capability validate and mobile permission audits against targeted build architectures.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Mobile Plugin Scoped Capability & ACL Enforcement

Tauri 2.0 Mobile Plugin Scoped Capability & ACL Enforcement defines an industrial-grade behavioral standard for mobile engineering. Enforces granular compile-time capabilities and runtime ACL scoping for Tauri 2.0 iOS and Android plugin bridges. Prevents arbitrary IPC bridge privilege escalation by prohibiting un-scoped default plugin sets and wildcards across webview execution 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: Over-privileged IPC bridges granting broad runtime filesystem, biometric, or hardware access across mobile webview boundaries. 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 bridges granting broad runtime filesystem, biometric, or hardware access across mobile webview boundaries.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 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 isolated capabilities per window and mobile platform in `src-tauri/capabilities/*.json` instead of using root default configs.

Engineers MUST ALWAYS declare isolated capabilities per window and mobile platform in `src-tauri/capabilities/*.json` instead of using root default configs.

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 NEVER use `*

Engineers MUST NEVER use `*:default` or un-scoped capability sets (e.g., `fs:default` without a path scope array) in mobile deployment targets.

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 MUST strictly scope plugin access to mobile sandbox directories (`$APPDATA`, `$RESOURCE`, `$CACHE`) using `BaseDirectory` enums rather than arbitrary string paths.

Code MUST strictly scope plugin access to mobile sandbox directories (`$APPDATA`, `$RESOURCE`, `$CACHE`) using `BaseDirectory` enums rather than arbitrary string paths.

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 verify runtime permission status via plugin-specific `checkPermissions()` and `requestPermissions()` before dispatching IPC invocations on Android/iOS.

Services MUST verify runtime permission status via plugin-specific `checkPermissions()` and `requestPermissions()` before dispatching IPC invocations on Android/iOS.

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, untyped `invoke('plugin

Components NEVER invoke raw, untyped `invoke('plugin:...')` commands bypassing the compiled Tauri 2.0 mobile client SDK.

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 Plugin Scoped Capability & ACL Enforcement critical for AI coding assistants?

Enforces granular compile-time capabilities and runtime ACL scoping for Tauri 2.0 iOS and Android plugin bridges. Prevents arbitrary IPC bridge privilege escalation by prohibiting un-scoped default plugin sets and wildcards across webview execution 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 (Over-privileged IPC bridges granting broad runtime filesystem, biometric, or hardware access across mobile webview boundaries.) 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