I would not only be okay with the MCP allow list being active in “Ask every time” mode — I would actually strongly welcome it.
Being able to explicitly pre-approve individual MCP tools while staying in “Ask every time” mode is, in my view, highly desirable.
In fact, this could even be considered a feature request on its own.
However, the current behavior makes it look as if this is already the intended design — just implemented inconsistently.
The contradiction arises here:
The allow list appears to grant persistent permission to certain MCP tools, even in “Ask every time” mode
At the same time, the Skip action is still presented to the user
Clicking Skip, however, does not reliably prevent execution
This results in an unclear mental model for users. If allow-listed tools are meant to bypass confirmation, then Skip should not be shown.
If Skip is shown, it must always be authoritative and cancel execution.
Hey, thanks for the detailed report - the 3-phase reproduction really helps.
This is a known issue. Right now, the Allow List overrides “Ask every time” mode - tools from the whitelist run even if you click Skip. The team knows about it.
Workaround for now: remove the tool from the Allow List when you need full control via Skip/Accept.
About your comment in Post #3 - that’s valid feedback. It’s unclear right now: if Allow List gives implicit permission, the Skip button shouldn’t show. If Skip shows, it should work. The current behavior confuses users. I’ll pass it to the team along with this report.
Let me know if the workaround doesn’t fit your case.
One follow-up question though:
Is it planned (or at least being considered) to support a whitelist / allow list that is still respected when running in “Ask Every Time” mode?
From a user perspective, this would be extremely helpful: being able to explicitly trust certain MCP servers or tools while still keeping the general safety net of manual confirmation for everything else. The current behavior almost feels like this might already be the intended direction, which is why I wanted to ask.
Thanks again for the clarification and for taking the time to look into this.