Execute_sql not showing SQL code for review, until after it runs the code. Don't want to give permission to unknown code

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Can’t click on a command an agent is running to see the SQL it plans to run. I can click on it after it has ran, to see the details. Just not when it is asking me if it can run it.
I used to be able to click on the command it was asking for permission and see the details.

Steps to Reproduce

I open up cursor and ask it to run SQL using my Supabase/Postgres MCP.
It says “running execute_sql in supabase” and asks for permission to run it.
I can’t click on it to show details.
I don’t want to give it permission to run SQL against my db that I can’t review first.

Screenshots / Screen Recordings

Screenshot 2026-07-15 140131.png
Screenshot 2026-07-15 140131.png632×116 3.07 KB

Operating System

Windows 10/11

Version Information

Version: 3.11.19 (user setup)
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

6

This is a known regression, not intended. A recent change to how tool calls render stopped surfacing MCP arguments on the approval prompt, so there’s currently no in-UI way to review the input (your SQL) before approving. The details come back once the call has run. We’ve reported it to the team and it’s on our radar.

Until it’s fixed, for a write-capable tool like Supabase execute_sql: keep it off Always Run so you keep the Skip option, and ask the agent to state the exact SQL in chat before it calls the tool, so you can verify and Skip if it’s not what you want.

Tracking the same issue here, so I’ll post updates there: Can not see call args in mcp tool calls