Implement after the fact review system

In my dayjob I am allowed to use Github Copilot and other chat tools to
enrich my developer experience. Some employers are okay with me using
Jira & Concluence MCPs, but I don't like using them.

When i ask confluence "The first feature" then the Confluence API will
perform a search for "The first feature", but also "The", "first" or
"feature", which can drag in IP that I'd rather not share with an
internet based LLM.

With this pull request I'm adding more granular control over tool
execution. When a tool is executed a new option is available "yes &
review". when this option is picked, then the tool will execute like
normal, but show a window to the user prompting them to read through the
text that is going to be fed back to the LLM. if the user is not
comfortable with the result returned (or if the result returned would
steer the LLM into the wrong direction; or worse includes rather clear prompt
poisoning/injection ) then the user can simply just reject the returned
result and it will never be fed into the LLM.

Author: HendrikPetertje

README.md

@@ -61,8 +61,12 @@ MCP Hub is a MCP client for neovim that seamlessly integrates [MCP (Model Contex
 | | Headers | ✅ | For API keys/tokens |
 | **Chat Integration** ||||
 | | [Avante.nvim](https://github.com/yetone/avante.nvim) | ✅ | Tools, resources, resourceTemplates, prompts(as slash_commands) |
-| | [CodeCompanion.nvim](https://github.com/olimorris/codecompanion.nvim) | ✅ | Tools, resources, templates, prompts (as slash_commands), 🖼 image responses | 
+| | [CodeCompanion.nvim](https://github.com/olimorris/codecompanion.nvim) | ✅ | Tools, resources, templates, prompts (as slash_commands), 🖼 image responses, 🔒 tool result review | 
 | | [CopilotChat.nvim](https://github.com/CopilotC-Nvim/CopilotChat.nvim) | ✅ | Tools, resources, function calling support |
+| **Security & Control** ||||
+| | Tool Confirmation | ✅ | User confirmation before tool execution |
+| | Result Review | ✅ | Inspect & approve/reject tool results before sending to LLM |
+| | Granular Auto-Approval | ✅ | Per-server, per-tool, or function-based approval rules |
 | **Marketplace** ||||
 | | Server Discovery | ✅ | Browse from verified MCP servers |
 | | Installation | ✅ | Manual and auto install with AI |

doc/extensions/codecompanion.md

@@ -156,12 +156,30 @@ If `make_slash_commands = true`, MCP prompts are available as slash commands:
 
 
 
-## Auto-Approval
+## Tool Approval & Review
 
 By default, whenever codecompanion calls `use_mcp_tool` or `access_mcp_resource` tool or a specific tool on some MCP server, it shows a confirm dialog with tool name, server name and arguments.
 
 ![Image](https://github.com/user-attachments/assets/201a5804-99b6-4284-9351-348899e62467)
 
+### Review Tool Results
+
+The confirmation dialog now includes a **"Yes & Review"** option, allowing you to inspect tool results before they're sent to the LLM. This is particularly useful for preventing sensitive data leakage when working with tools that access confidential information (JIRA, Confluence, databases, etc.).
+
+**Keyboard shortcuts in confirmation dialog:**
+- `y`/`Y` - Yes (execute and auto-send to LLM)
+- `r`/`R` - **Yes & Review** (execute, then show review window)
+- `n`/`N` - No (don't execute)
+- `c`/`C` or `<Esc>` - Cancel
+
+When you select "Yes & Review", the tool executes and then displays a review window where you can:
+- Inspect the full result (with scrolling for large outputs)
+- Approve to send to LLM (`y`, `a`, or `<CR>` on Approve)
+- Reject to prevent data leakage (`n`, `r`, or `<Esc>`)
+
+**See the full documentation**: [Tool Result Review Feature](/other/review-feature)
+
+### Auto-Approval
 
 #### Fine-Grained Auto-Approval
 
@@ -239,6 +257,11 @@ require("mcphub").setup({
             end
         end
 
+        -- Execute JIRA/Confluence tools but always review results
+        if params.server_name == "jira" or params.server_name == "confluence" then
+            return { approve = true, review = true }
+        end
+
         -- Check if tool is configured for auto-approval in servers.json
         if params.is_auto_approved_in_server then
             return true -- Respect servers.json configuration
@@ -258,8 +281,9 @@ require("mcphub").setup({
 - `params.is_auto_approved_in_server` - Boolean indicating if tool is configured for auto-approval in servers.json
 
 **Return values:**
-- `true` - Auto-approve the call
-- `false` - Show confirmation prompt
+- `true` - Auto-approve and execute immediately (no review)
+- `false` - Show confirmation prompt (user can choose review)
+- `{ approve = true, review = true }` - Execute and force review window
 - `string` - Deny with error message
 - `nil` - Show confirmation prompt (same as false)
 

doc/mcphub.txt

@@ -1,4 +1,4 @@
-*mcphub.nvim.txt*        For NVIM v0.10.0        Last change: 2025 December 12
+*mcphub.nvim.txt*        For NVIM v0.10.0        Last change: 2026 February 17
 
 ==============================================================================
 Table of Contents                              *mcphub.nvim-table-of-contents*
@@ -3295,13 +3295,36 @@ If `make_slash_commands = true`, MCP prompts are available as slash commands:
 _Example: Using an MCP prompt via slash command_:
 
 
-AUTO-APPROVAL ~
+TOOL APPROVAL & REVIEW ~
 
 By default, whenever codecompanion calls `use_mcp_tool` or
 `access_mcp_resource` tool or a specific tool on some MCP server, it shows a
 confirm dialog with tool name, server name and arguments.
 
 
+REVIEW TOOL RESULTS
+
+The confirmation dialog now includes a **“Yes & Review”** option, allowing
+you to inspect tool results before they’re sent to the LLM. This is
+particularly useful for preventing sensitive data leakage when working with
+tools that access confidential information (JIRA, Confluence, databases, etc.).
+
+**Keyboard shortcuts in confirmation dialog:** - `y`/`Y` - Yes (execute and
+auto-send to LLM) - `r`/`R` - **Yes & Review** (execute, then show review
+window) - `n`/`N` - No (don’t execute) - `c`/`C` or `<Esc>` - Cancel
+
+When you select "Yes & Review", the tool executes and then displays a review
+window where you can: - Inspect the full result (with scrolling for large
+outputs) - Approve to send to LLM (`y`, `a`, or `<CR>` on Approve) - Reject to
+prevent data leakage (`n`, `r`, or `<Esc>`)
+
+**See the full documentation**: Tool Result Review Feature
+</other/review-feature>
+
+
+AUTO-APPROVAL
+
+
 FINE-GRAINED AUTO-APPROVAL
 
 For fine-grained control, configure auto-approval per server or per tool in
@@ -3378,6 +3401,11 @@ specific tool call:
                 end
             end
 
+            -- Execute JIRA/Confluence tools but always review results
+            if params.server_name == "jira" or params.server_name == "confluence" then
+                return { approve = true, review = true }
+            end
+    
             -- Check if tool is configured for auto-approval in servers.json
             if params.is_auto_approved_in_server then
                 return true -- Respect servers.json configuration
@@ -3395,9 +3423,10 @@ resources) - `params.arguments` - Table of arguments passed to the tool -
 - Resource URI (for resource access) - `params.is_auto_approved_in_server` -
 Boolean indicating if tool is configured for auto-approval in servers.json
 
-**Return values:** - `true` - Auto-approve the call - `false` - Show
-confirmation prompt - `string` - Deny with error message - `nil` - Show
-confirmation prompt (same as false)
+**Return values:** - `true` - Auto-approve and execute immediately (no review)
+- `false` - Show confirmation prompt (user can choose review) - `{ approve =
+true, review = true }` - Execute and force review window - `string` - Deny with
+error message - `nil` - Show confirmation prompt (same as false)
 
 
 AUTO-APPROVAL PRIORITY