[FEATURE] Claude Cowork 3P’s managedMcpServers should support glob-syntax for toolPolicy

Resolved 💬 3 comments Opened May 11, 2026 by merlin83 Closed Jun 10, 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

We are using Claude Desktop 3P with Cowork with our litellm gateway.

Many of the managedMcpServers that we deploy to our users have a lot of tools and many of them are regularly being updated.

We can’t whitelist each and every tool across all the mcp servers, and since this is an enterprise deployment, most of them are internal mcp servers and we are good to allow all of the tools anyway.

Proposed Solution

Can we have a feature to allow all tools from each mcp server instead of the current toolPolicy which requires each tool to be individually named.

Either a glob syntax such as toolPolicy: {“*”: “allow”} or just a string toolPolicy: “allow”

Thanks!

Alternative Solutions

For now, one option we are considering is to pre-generate the toolPolicy for all tools in each mcp server. However, this is not ideal as the mcp servers are owned by different teams and are regularly being updated.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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