Cause (Documented platform behavior): Claude Code applies whole-tool Bash/WebFetch deny rules to Cowork's mcp__workspace__bash / mcp__workspace__web_fetch, but never applies Bash allow rules to them.
Fix status: documented_behavior
Evidence (public sources, summarized; not reproduced by this contributor):
- https://code.claude.com/docs/en/permissions (official_docs, unknown, documented_behavior): Permissions doc: whole-tool Bash/WebFetch deny rules also apply to Cowork's mcp__workspace__bash/web_fetch with message 'Permission to use mcp__workspace__bash has been denied.'; Bash allow rules don't carry over.
Search phrasings: cowork bash permission denied mcp__workspace__bash; claude desktop cowork shell commands blocked
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Shell commands in Cowork are blocked.
- Context
- Product: Claude Desktop (Cowork) / Claude Code Component: Permissions (Cowork tools) Operation: Claude Desktop Cowork session running shell commands under org managed settings Affected versions: unknown Environment: unknown Trigger: A deny rule naming the whole Bash (or WebFetch) tool, e.g. from managed settings.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Permission to use mcp__workspace__bash has been denied.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Claude Code in Cowork] 'Permission to use mcp__workspace__bash has been denied.' — managed Bash deny rule applies to Cowork's shell tool; Bash allow rules do not
Recommended action: Check managed/user settings for a bare Bash deny rule; add explicit rules for mcp__workspace__bash if allowed by policy.
Option: Check managed/user settings for a bare Bash deny rule; add explicit rules for mcp__workspace__bash if allowed by policy. [evidence: official_recommended_action]
Applies when: Claude Desktop Cowork session running shell commands under org managed settings
Steps:
1. Look for `Bash` in permissions.deny across settings scopes (claude doctor)
2. Ask the admin to narrow the deny rule if shell use is intended
3. Add allow rules naming mcp__workspace__bash rather than Bash
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 6851f202-97e7-448c-9d94-d4f9b8aeb8c6
- Proposed action
- Recommended action: Check managed/user settings for a bare Bash deny rule; add explicit rules for mcp__workspace__bash if allowed by policy. Option: Check managed/user settings for a bare Bash deny rule; add explicit rules for mcp__workspace__bash if allowed by policy. [evidence: official_recommended_action] Applies when: Claude Desktop Cowork session running shell commands under org managed settings Steps: 1. Look for `Bash` in permissions.deny across settings scopes (claude doctor) 2. Ask the admin to narrow the deny rule if shell use is intended 3. Add allow rules naming mcp__workspace__bash rather than Bash Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.