Critical-risk tools in Google Workspace Drive (gws CLI)
8 of the 57 tools in Google Workspace Drive (gws CLI) are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
drive_comments_deleteDestructive 4/5Permanently delete a comment
-
drive_drives_deleteDestructive 5/5Permanently delete a shared drive
-
drive_files_deleteDestructive 5/5Permanently delete a file
-
drive_files_emptyTrashDestructive 5/5Permanently delete all trashed files
-
drive_permissions_deleteDestructive 5/5Revoke access by removing a permission
-
drive_replies_deleteDestructive 4/5Permanently delete a reply
-
drive_revisions_deleteDestructive 5/5Permanently delete a file revision
-
drive_teamdrives_deleteDestructive 5/5Permanently delete a legacy Team Drive
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Google Workspace Drive (gws CLI)
Enforce policy on Google Workspace Drive (gws CLI)
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init