Understanding Low Stake Actions in Custom Pipedrive MCP Server

Hey Team, Context : Currently playing around with a custom Pipedrive MCP server (hosted in n8n), for my daily preparation meeting. Running : Calling my agent for looking at my calendar, then triggering another agent which is looking in my CRM deals. I've got an authorization popup asking to grant tool usage on Search a deal, whereas the dedicated Tool stake settings is set as "Low". Question : From Dust's documentation (here), especialy this sentence "A Low stake action can be silenced by the user at their own will. Once they silence the tool, they won't see the validation pop-ups anymore, and the action will execute automatically." Does it mean that I need to always test every action in low stake state before, in order for me to approve all action once and for all ? Thanks for any highlights