Critical Risk →

drive_files_emptyTrash

Permanently delete all trashed files

Bulk permanent deletion, cannot be undone

Part of the Google Workspace Drive (gws CLI) MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@gws mcp -s drive Destructive Risk 5/5

AI agents may call drive_files_emptyTrash to permanently remove or destroy resources in Google Workspace Drive (gws CLI). Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call drive_files_emptyTrash in a loop, permanently destroying resources in Google Workspace Drive (gws CLI). There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

google-workspace-drive.yaml
tools:
  drive_files_emptyTrash:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Google Workspace Drive (gws CLI) policy for all 57 tools.

Tool Name drive_files_emptyTrash
Category Destructive
Risk Level Critical

View all 57 tools →

Agents calling destructive-class tools like drive_files_emptyTrash have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

drive_files_emptyTrash is one of the critical-risk operations in Google Workspace Drive (gws CLI). For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the drive_files_emptyTrash tool do? +

Permanently delete all trashed files. It is categorised as a Destructive tool in the Google Workspace Drive (gws CLI) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on drive_files_emptyTrash? +

Add a rule in your Intercept YAML policy under the tools section for drive_files_emptyTrash. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Workspace Drive (gws CLI) MCP server.

What risk level is drive_files_emptyTrash? +

drive_files_emptyTrash is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drive_files_emptyTrash? +

Yes. Add a rate_limit block to the drive_files_emptyTrash rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block drive_files_emptyTrash completely? +

Set action: deny in the Intercept policy for drive_files_emptyTrash. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides drive_files_emptyTrash? +

drive_files_emptyTrash is provided by the Google Workspace Drive (gws CLI) MCP server (@gws mcp -s drive). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Google Workspace Drive (gws CLI)

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.