# trash_file

action=trash moves a file (or folder, with everything inside) to the Drive trash; action=restore brings it back. Trashing is REVERSIBLE — the file stays recoverable until the trash auto-purges it after ~30 days — and is the safe default whenever a user asks to 'delete' something: only use delete_file_forever when they explicitly want it gone beyond recovery. Trashed files disappear from search_files unless include_trashed=true. Only the owner (or a shared-drive member with the right role) can trash; restore puts the file back at its old parent. Returns id, name, trashed and explicitlyTrashed.

Agent View of the PolicyLayer registry record for `trash_file`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-drive/trash-file

## Facts

- Tool: `trash_file`
- Server: Mcp Google Drive (`@a1-x-tech/mcp-google-drive`) — https://policylayer.com/tools/a1-x-tech-mcp-google-drive.md
- Install: `npx -y @a1-x-tech/mcp-google-drive`
- Homepage: https://github.com/A1-x-Tech/mcp-google-drive
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | yes | trash = move to the trash (reversible); restore = take it back out. |
| `file_id` | string | yes | The file id — the long id from the Drive URL (drive.google.com/file/d/<fileId> or docs.google.com/.../d/<fileId>/edit) or from search_files/get_file output. Fol |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trash_file",
    "arguments": {
      "action": "<action>",
      "file_id": "<file_id>"
    }
  }
}
```

## Why trash_file is rated Critical

An AI agent that decides to call trash_file doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Drive is gone. There is no undo for destructive operations.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call trash_file to permanently remove resources in Mcp Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Google Drive:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "trash_file"
  ]
}
```

## Other tools on Mcp Google Drive (14)

- `delete_file_forever` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/delete-file-forever.md
- `manage_comments` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/manage-comments.md
- `manage_permissions` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/manage-permissions.md
- `raw_request` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/raw-request.md
- `download_file` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/download-file.md
- `get_file` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/get-file.md
- `list_shared_drives` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/list-shared-drives.md
- `search_files` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/search-files.md
- `copy_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/copy-file.md
- `create_folder` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/create-folder.md
- `export_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/export-file.md
- `move_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/move-file.md
- `update_file_metadata` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/update-file-metadata.md
- `upload_file` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-drive/upload-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1-x-tech-mcp-google-drive · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-drive