How to enable mcp tool approval dialog? #4854

Activity

1. github-actions commented on Nov 28, 2025

   

   github-actionsBot

   on Nov 28, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • feat: Add Permission Control for MCP Tools #2748: Add Permission Control for MCP Tools - Addresses the exact same concern about MCP tools bypassing the permission system
   • how to specify permissions for mcp servers #2899: How to specify permissions for mcp servers - Related question about MCP server permissions
   • Implement permissions in TUI #239: Implement permissions in TUI - General permission system request
   • Feature Request: Add "ask before editing files" mode #935: Feature Request: Add "ask before editing files" mode - Proposes an "ask" mode for tool execution (similar to what you're requesting)
   • Agent should request permission before reading or editing files #3205: Agent should request permission before reading or editing files - Related permission request for file operations

   Feel free to ignore if none of these address your specific case.
2. rekram1-node commented on Dec 2, 2025

   

   rekram1-node

   on Dec 2, 2025

   Contributor

   More actions

   we need to expand permissions to work for all tools, currently not possible (unless you do this via plugin)
3. nitg16 commented on Dec 5, 2025

   

   nitg16

   on Dec 5, 2025

   Author

   More actions

   How to do this via plugin? I arrived at this code after reading docs, but how to proceed further?

   export const McpApproval = async ({ project, client, $, directory, worktree }) => {
     return {
       "tool.execute.before": async (input, output) => {
         if (input.tool.startsWith("mcp_")) {
           // What to do here? How to show approval dialog in TUI?
         }
       },
     }
   }
4. JeminiRiver commented on Dec 7, 2025

   

   JeminiRiver

   on Dec 7, 2025

   More actions

   I keep circling back to this need. I've been compensating with hyper specific agent access but it's imperfect and leave's me disabling some mcp tools permanently. I've got a local build running with a real slim quick permissions add for mcp that sits beside and works identically to bash permissions. I'll see how it tests out tomorrow. I'll be happy for a permanent fix though because this has defiantly been a pain point.

   👍React with 👍3Reacted by nitg16, pypeaday and Jan-Henrik Damaschke
5. nitg16 commented on Jan 7, 2026

   

   nitg16

   on Jan 7, 2026

   Author

   More actions

   Any update on this? I see a new permission system. But it is not clear from docs if it covers mcp.
6. 0byte-coding commented on Jan 9, 2026

   

   0byte-coding

   on Jan 9, 2026

   More actions

   Any update on this? I see a new permission system. But it is not clear from docs if it covers mcp.

   it does, check https://opencode.ai/docs/tools/#configure

   👍React with 👍2Reacted by nitg16 and Jema Willis
7. nitg16 commented on Jan 9, 2026

   

   nitg16

   on Jan 9, 2026

   Author

   More actions

   Any update on this? I see a new permission system. But it is not clear from docs if it covers mcp.

   it does, check https://opencode.ai/docs/tools/#configure

   Thanks, will check it out.
8. rekram1-node commented on Jan 9, 2026

   

   rekram1-node

   on Jan 9, 2026

   Contributor

   More actions

   This is possible in new permission system, here is an example:

   

   🚀React with 🚀2Reacted by Miguel Crespo and FlavioLimaMindera
9. rekram1-node

   closed this as completedon Jan 9, 2026