Bug: Wildcard Permission Matching Fails for Some MCP Tools
Resolved 💬 4 comments Opened Feb 24, 2026 by vermavikrant Closed Mar 24, 2026
Bug Report: Wildcard Permission Matching Fails for Some MCP Tools
Description:
Wildcard patterns in settings.json permissions don't work consistently for MCP tools. Specifically, mcp__linear__list_* and mcp__linear__get_* patterns fail to match tools like mcp__linear__list_issues, causing unexpected permission prompts despite explicit wildcard permissions.
Environment:
- OS: macOS (Darwin 25.3.0)
- Shell: zsh
- Claude Code version: [latest as of 2026-02-23]
Steps to Reproduce:
- Add wildcard permissions to
~/.claude/settings.json:
"allow": [
"mcp__linear__list_*",
"mcp__linear__get_*"
]
- Attempt to use
mcp__linear__list_issuestool - Claude Code prompts for permission despite the wildcard match
Expected Behavior:mcp__linear__list_* should match mcp__linear__list_issues and allow the tool without prompting.
Actual Behavior:
Permission prompt appears, requiring explicit permission for mcp__linear__list_issues.
Workaround:
Add explicit permissions instead of wildcards:
"allow": [
"mcp__linear__list_issues",
"mcp__linear__get_issue",
...
]
Additional Context:
- Wildcard patterns work correctly for other MCP servers when tested, suggesting the issue is specific to certain MCP tool naming patterns or servers
- The inconsistent behavior makes it difficult to predict which wildcards will work reliably
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗