anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Ability to restrict MCP tool use to subagent only #1514

New Issue
Closed
opened 2026-02-16 17:31:20 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:31:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @garrett-hopper on GitHub (Aug 27, 2025).

Currently builtin tools (edit, bash, webfetch) can be disabled at the top-level using permissions. It would be useful to have the ability to do the same with MCP tools as well.
The primary use case is to disable large/complex MCP servers (Github MCP for example) from the top-level agent and restrict their use to a subagent.

Side note: permissions and tools seem to have some overlap, specifically for subagents? ("deny" in permissions would be the same as setting the "tools" entry to false, right?)

Originally created by @garrett-hopper on GitHub (Aug 27, 2025). Currently builtin tools (`edit`, `bash`, `webfetch`) can be disabled at the top-level using [permissions](https://opencode.ai/docs/permissions/#tool-permission-support). It would be useful to have the ability to do the same with MCP tools as well. The primary use case is to disable large/complex MCP servers (Github MCP for example) from the top-level agent and restrict their use to a subagent. Side note: permissions and tools seem to have some overlap, specifically for subagents? ("deny" in permissions would be the same as setting the "tools" entry to false, right?)
yindo closed this issue 2026-02-16 17:31:20 -05:00
yindo commented 2026-02-16 17:31:21 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 27, 2025):

This issue might be related to existing issues. Please check:

  • #2172: Feature Request: Limiting number of MCP tools based on configuration (addresses MCP tool restrictions, but focuses on quantity limits rather than scope restriction to subagents)
  • #1961: Unifying tools and permissions (discusses the overlap between permissions and tools configuration that you mentioned in your side note)
  • #514: Option to Enable / Disable MCP Servers (via TUI) (about disabling MCP servers, but at runtime via TUI rather than configuration-based subagent restriction)

Feel free to ignore if none of these address your specific case of restricting MCP tools to subagent-only use.

@github-actions[bot] commented on GitHub (Aug 27, 2025): This issue might be related to existing issues. Please check: - #2172: Feature Request: Limiting number of MCP tools based on configuration (addresses MCP tool restrictions, but focuses on quantity limits rather than scope restriction to subagents) - #1961: Unifying tools and permissions (discusses the overlap between permissions and tools configuration that you mentioned in your side note) - #514: Option to Enable / Disable MCP Servers (via TUI) (about disabling MCP servers, but at runtime via TUI rather than configuration-based subagent restriction) Feel free to ignore if none of these address your specific case of restricting MCP tools to subagent-only use.
yindo commented 2026-02-16 17:31:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 27, 2025):

@garrett-hopper
You can do this already?

At top level config set

"tools": {
  "context7*": false
}

then for any agent definition set:

"tools": {
  "context7*": true
}
@rekram1-node commented on GitHub (Aug 27, 2025): @garrett-hopper You can do this already? At top level config set ``` "tools": { "context7*": false } ``` then for any agent definition set: ``` "tools": { "context7*": true } ```
yindo commented 2026-02-16 17:31:21 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 27, 2025):

Side note: permissions and tools seem to have some overlap, specifically for subagents? ("deny" in permissions would be the same as setting the "tools" entry to false, right?)

yes this is true and that's why they need to get merged soon

@rekram1-node commented on GitHub (Aug 27, 2025): > Side note: permissions and tools seem to have some overlap, specifically for subagents? ("deny" in permissions would be the same as setting the "tools" entry to false, right?) yes this is true and that's why they need to get merged soon
yindo commented 2026-02-16 17:31:21 -05:00
Author
Owner
Copy Link
Copy Source

@garrett-hopper commented on GitHub (Aug 27, 2025):

🤦 Not sure how I missed the ability to use tools at top level; thought it was subagent specific. Sorry for the noise.
(Got it in my head that permissions was the only option and should somehow support MCP I think.)

@garrett-hopper commented on GitHub (Aug 27, 2025): 🤦 Not sure how I missed the ability to use tools at top level; thought it was subagent specific. Sorry for the noise. (Got it in my head that permissions was the only option and should somehow support MCP I think.)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1514
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?