A visual macro cannot reliably tell whether a confirmation refers to the expected file, record, amount, recipient, or permission.
The safer default is no
Usually not without supervision. Confirmation buttons exist to stop accidental or consequential actions, so automatic clicking should be limited to controlled testing or harmless internal workflows.
Use disposable test data
If the task is a staging test, MacroLoop can record the confirmation path against disposable data. Keep the final production confirmation outside the recording.
Confirmations that need a person
Never automate purchases, refunds, deletions, permission grants, legal acceptance, or messages to real recipients merely because the button appears in the usual location.
THE TAKEAWAY
Automate preparation when useful, but keep consequential confirmation under human control.