Allow editing MCP tool call content before execution when permission is 'ask' #23790

Summary

When a tool call requires approval via the permission: "ask" config (especially MCP tools like Confluence/Jira), the user can only approve or reject the call. There's no way to edit the content before it's sent.

Use Case

For MCP tools like Atlassian (Jira/Confluence), the agent might draft a page body, issue description, or comment that's close but needs tweaks. Currently the only options are:

1. Approve as-is
2. Reject and re-prompt the agent

It would be much more efficient to edit the tool call parameters (e.g., the body of a Confluence page, the description of a Jira issue) before approving.

Proposed Behavior

When a tool call is prompted for approval and the user selects "ask":

• Add an "edit" option alongside "once", "always", and "reject"
• Selecting "edit" opens the tool call parameters in the user's $EDITOR (or a TUI text field)
• After saving, the modified parameters are used for the tool call

This would be especially valuable for MCP tools where the content being created (wiki pages, issue descriptions, comments) is user-facing and often needs human refinement.