tauri-scope_skill

Overview

This skill guides you through configuring Tauri v2 command scopes to secure command and resource access. It covers filesystem and HTTP scope patterns, dynamic runtime scope management, remote URL capabilities, and practical configuration examples. The content focuses on actionable rules you can apply to capability files and Rust code to enforce least privilege.

How this skill works

Scopes are declared in capability JSON or TOML files and passed to commands at runtime. Commands must validate and enforce the provided scopes; deny rules take precedence over allow rules. Filesystem scopes use glob-compatible path patterns and runtime-injected path variables, while HTTP scopes use URL patterns. Dynamic scope changes can be made safely from Rust via FsExt with explicit validation.

When to use it

• When you need fine-grained control over which filesystem paths a command may access
• When restricting outbound network access to specific APIs or domains
• When you must prevent access to sensitive directories inside otherwise allowed paths
• When granting temporary or user-approved access at runtime
• When defining reusable permission sets for multiple windows or platforms

Best practices

• Minimize scopes: allow only the exact paths or URLs your feature requires
• Use deny rules to explicitly block sensitive folders even inside allowed globs
• Prefer command-specific permissions instead of broad global scopes
• Validate and sanitize any path or URL before expanding scopes at runtime
• Use injected path variables (e.g., $APPDATA, $DOCUMENT) instead of hardcoded paths
• Audit command implementations: enforce scope checks server-side in your command code

Example use cases

• Allow read-only access to application data: permit $APPDATA/** for read commands and deny sensitive subfolders
• Limit HTTP access to backend APIs and CDNs using https://api.example.com/\* and https://*.cdn.example.com/**
• Restrict document editing to $DOCUMENT/** while denying hidden files or private key patterns
• Dynamically allow a user-selected directory for file import after verifying existence and intent
• Define a permission set that combines recursive appdata access with deny rules for .ssh and .gnupg