Hey there,
You’re right, and this isn’t something on your end. A recent change to how tool calls render stopped surfacing MCP arguments, and on the approval prompt they aren’t shown at all right now, so there’s currently no in-UI way to review the input (like the execute_sql SQL) before you allow or deny. I’ve reproduced it on my side and reported it to the team.
On the setting: the Conversation Density “Detailed” option won’t bring it back. It only changes how completed tool calls are grouped in the transcript, not what the approval prompt shows, so that one is a bit of a red herring here.
Until it’s fixed, your instinct about writing the call out first is the safest approach:
- Keep risky Supabase tools (like
execute_sql) off Always Run, so you always get the Skip option instead of an auto-approve. - Ask the agent to state the exact SQL and arguments in chat before it calls the tool, so you can review them and then approve.
I’m going to fold this into the main thread where we’re already tracking the same issue, so all the reports stay together and you’ll see updates in one place: Can not see call args in mcp tool calls. I’ll post there as soon as there’s progress.