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