Support wildcard patterns in permission settings for dynamic temporary file paths

Problem

MCP servers like Chrome DevTools create temporary directories with random hash names (e.g., /var/folders/.../T/chrome-devtools-mcp-abc123/screenshot.png). Currently, even with wildcard permissions like Read(/var/folders/**), each unique temporary directory requires manual approval.

Requested Feature

Support wildcard patterns that can match dynamic path segments, such as:

• Read(/var/folders/.../T/chrome-devtools-mcp-*/screenshot.png)
• Read(/var/folders/.../T/chrome-devtools-mcp-*/**)

This would allow users to grant blanket permission for all files created by specific MCP servers without approving each unique temporary directory.

Use Case

When using Chrome DevTools MCP for browser automation and testing, screenshots are frequently captured. Currently, this requires approving each screenshot read, which disrupts workflow significantly.

Current Workaround Attempts

• Adding patterns like Read(/var/folders/**) - still prompts for each unique temp directory
• Adding Read(/var/folders/4m/jfkg0vbx1b74k9kgwcdmznp40000gn/T/chrome-devtools-mcp-*/**) - doesn't work with asterisk wildcards
• Adding each unique path manually - not scalable as temp directories are randomly generated

Expected Behavior

Once a wildcard pattern is approved, all matching paths (including those with dynamic segments) should be auto-approved without user intervention.