MCP Elicitation approval dialog cannot safely review or scroll long command arguments

What platform are you using?

Codex Desktop on Windows with an HTTP MCP server using MCP Elicitation.

What issue are you seeing?

The confirmation dialog for a SYSTEM-level MCP command displays the tool arguments as raw JSON. For a long PowerShell command:

• the script is rendered as one dense escaped JSON string;
• quotes appear as escape sequences such as \u0027;
• logical statements are not formatted on separate lines;
• the command can exceed the available modal height;
• no usable scrollbar or keyboard-accessible scrolling mechanism is apparent;
• the confirmation controls remain visible, but the user cannot confidently review the complete command.

The dialog title was equivalent to “Run this exact command as Windows LocalSystem?” and the payload contained executable, a long arguments array, workingDirectory, and timeoutSeconds.

Steps to reproduce

1. Connect an MCP server that requests confirmation through Elicitation.
2. Request execution of PowerShell with -Command containing a long multi-statement script.
3. Open the resulting approval dialog in Codex Desktop.
4. Attempt to inspect the complete command and its exact targets.
5. Observe that the content is dense, escaped, may not fit in the modal, and cannot be conveniently scrolled.

Expected behavior

The approval UI should make the complete request reviewable before consent:

• place the payload in a vertically and horizontally scrollable region;
• support mouse wheel, scrollbar, keyboard, selection, and copying;
• keep action buttons in a sticky footer;
• syntax-format executable, individual arguments, working directory, and timeout;
• render long script arguments as multiline code rather than an escaped JSON string;
• show a concise risk summary and affected paths above the raw request;
• allow expanding/collapsing the exact raw payload;
• clearly indicate when content extends beyond the visible area;
• never permit approval if part of the exact request is inaccessible.

Actual behavior

A large raw JSON block fills the dialog. The long script is difficult to parse and the user cannot reliably scroll through or review all of it before selecting Continue.

Safety impact

This is especially risky for privileged or destructive MCP tools. Confirmation is meaningful only when the user can inspect the complete executable, arguments, scope, and targets. A technically exact but practically unreadable payload encourages blind approval.

A screenshot reproducing the layout is available and can be supplied if maintainers need it.

Start by locating the MCP Elicitation approval dialog in Codex Desktop and reproduce the issue with a long PowerShell command containing multiple statements. Done means the complete executable, arguments, working directory, timeout, and raw payload remain accessible for review and copying, with scrolling and controls usable before approval.