You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Option to deny MCP tools by default #3612
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
(hope this wasnt suggested before, but did not find anything)
Context: I'd like to use certain MCP servers only with specific agents. E.g. I'm using the jetbrains mcp, but I don't want all agents to use it's file editing capabilities, since it does not work well with the undo feature.
However, I have created a Jetbrains agent for the purpose of collaborating closely on what I do in my current jetbrains IDE (think implement the open TODO() in my current editor).
Problem:
There seems to be no easy way to deny access to all MCP tools of a defined server globally and override this in only one agent.
I've tried setting "permissions" : { "jetbrains_*" : "deny"} in my global openapi.json to no success.
Also the "tools": { "jetbrains_*": false} was not supported globally.
So currently I'm stuck with disallowing the tools for each agent. This is cumbersome and errorprone, since we don't know which agents are going to be active depending on the project I'm working on.
Request:
Make either "tools" a global configuration, so I can disallow tool usage across all agents (with the expectation, that agent specific entries override this global config), or allow MCP tools to be referenced in the "permissions" (global) config.
Feature Request: Global default tools configuration for agents #2888: Feature Request: Global default tools configuration for agents - This closed issue requested exactly what you're asking for: a global way to control which tools are available by default to all agents, with the ability to override per agent
Ability to restrict MCP tool use to subagent only #2277: Ability to restrict MCP tool use to subagent only - This closed issue specifically requested the ability to disable MCP tools at the top level and restrict them to subagents only
The #2888 issue appears to be the most directly related to your request, as it proposed a 'defaultTools' configuration that would allow setting a baseline of available tools globally with per-agent overrides.
Feel free to ignore if none of these address your specific case.
Activity
rekram1-node commentedon Oct 31, 2025
@sroidl-airup the permissions wildcard support isn't there yet but the tools one should work globally, can u share your config?
Maybe do
opencode debug configgithub-actions commentedon Oct 31, 2025
This issue might be a duplicate of existing issues. Please check:
The #2888 issue appears to be the most directly related to your request, as it proposed a 'defaultTools' configuration that would allow setting a baseline of available tools globally with per-agent overrides.
Feel free to ignore if none of these address your specific case.
sroidl-airup commentedon Nov 3, 2025
My bad - I had a typo in the config. sorry to bother you!
fix: harden OpenCode adapter for Windows prompt delivery and MCP scoping