# move-to-trash

Move emails to trash

Agent View of the PolicyLayer registry record for `move-to-trash`. HTML page: https://policylayer.com/tools/0x8687-mcp-gmail-v1/move-to-trash

## Facts

- Tool: `move-to-trash`
- Server: Meme MCP Server (`0x8687/mcp-gmail-v1`) — https://policylayer.com/tools/0x8687-mcp-gmail-v1.md
- Homepage: https://github.com/0x8687/mcp-gmail-v1
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "move-to-trash",
    "arguments": {}
  }
}
```

## Why move-to-trash is rated Critical

Moving emails to trash is a destructive action — while some email systems allow recovery from trash within a time window, the operation removes emails from the inbox and is effectively irreversible if the trash is emptied. The blast radius is high because an AI agent could trash many important emails.

From the tool's own definition: "move-to-trash: Move emails to trash"

## Use case

AI agents call move-to-trash to permanently remove resources in Meme MCP Server, 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 Meme MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "move-to-trash"
  ]
}
```

## Other tools on Meme MCP Server (16)

- `check-gmail-connection` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/check-gmail-connection.md
- `get-email` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/get-email.md
- `get-emails` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/get-emails.md
- `get-gmail-settings` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/get-gmail-settings.md
- `get-labels` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/get-labels.md
- `get-threads` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/get-threads.md
- `search-emails` — Read — https://policylayer.com/tools/0x8687-mcp-gmail-v1/search-emails.md
- `connect-gmail` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/connect-gmail.md
- `create-draft` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/create-draft.md
- `create-label` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/create-label.md
- `forward-email` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/forward-email.md
- `mark-as-read` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/mark-as-read.md
- `mark-as-unread` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/mark-as-unread.md
- `reply-to-email` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/reply-to-email.md
- `send-draft` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/send-draft.md
- `send-email` — Write — https://policylayer.com/tools/0x8687-mcp-gmail-v1/send-email.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=0x8687-mcp-gmail-v1 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x8687-mcp-gmail-v1