[FEATURE] Support prefix wildcard for MCP tool permissions (e.g. mcp__server__get*)

Resolved 💬 4 comments Opened Apr 18, 2026 by KobiShikly Closed May 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary

Claude Code currently supports:

  • mcp__<server>__<tool> — exact tool
  • mcp__<server>__* — all tools on a server

There is no way to match a prefix subset, e.g. all read-only get* tools.

Motivation

Servers like atlassian-mcp expose both read-only tools (getJiraIssue, getConfluencePage…) and write tools (createJiraIssue, editJiraIssue…).

To pre-approve only safe tools today, users must list every tool explicitly (10+ lines). Using mcp__atlassian-mcp__* is too permissive — it also approves destructive tools.

Proposed Solution

Proposal

Support prefix/glob wildcards on the tool name segment:

"mcp__atlassian-mcp__get*",
"mcp__github-mcp__list_*",
"mcp__github-mcp__search_*"

This mirrors existing Bash(aws * get* *) wildcard support.

Alternative Solutions

Alternatives considered

  • Explicit list: verbose, breaks when new tools are added to the server.
  • mcp__server__*: too permissive.
  • PreToolUse hook: works but reimplements permission UX unnecessarily.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗