You'll notice
No documentation found
PowerShell dangerous-command detection now watches file and network cmdlets instead of browser executable names.
The set of PowerShell strings used for dangerous-command detection changed from browser executable names (chrome.exe, msedge.exe, firefox.exe, etc.) to file and network cmdlets (copy-item, move-item, compress-archive, expand-archive, invoke-webrequest, invoke-restmethod, new-item).
Names in the bundleinvoke-webrequestcopy-item
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Changed --add-dir, /add-dir, and additionalDirectories to refuse network paths (UNC shares, /net/<host> automounts) with a message before…