# gmail_delete_messages

Delete Gmail messages.

Agent View of the PolicyLayer registry record for `gmail_delete_messages`. HTML page: https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-delete-messages

## Facts

- Tool: `gmail_delete_messages`
- Server: Gmail MCP Server (`ampcome-mcps/gmail-mcp`) — https://policylayer.com/tools/ampcome-mcps-gmail-mcp.md
- Homepage: https://github.com/ampcome-mcps/gmail-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, 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": "gmail_delete_messages",
    "arguments": {}
  }
}
```

## Why gmail_delete_messages is rated Critical

Deletion of email messages is an irreversible operation that cannot be undone. Once deleted, messages are lost and cannot be recovered (barring Gmail's trash recovery window, which is time-limited).

From the tool's own definition: "Tool name contains 'delete' and description states 'Delete Gmail messages' — this permanently removes messages from the Gmail account."

## Use case

AI agents call gmail_delete_messages to permanently remove resources in Gmail 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 Gmail MCP Server:

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

## Other tools on Gmail MCP Server (7)

- `gmail_get_message` — Read — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-get-message.md
- `gmail_get_stats` — Read — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-get-stats.md
- `gmail_list_messages` — Read — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-list-messages.md
- `gmail_search_messages` — Read — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-search-messages.md
- `gmail_mark_as_read` — Write — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-mark-as-read.md
- `gmail_send_message` — Write — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-send-message.md
- `gmail_send_message_with_attachment` — Write — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-send-message-with-attachment.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=ampcome-mcps-gmail-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ampcome-mcps-gmail-mcp