# gmail_list_messages

List Gmail messages with optional search query.

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

## Facts

- Tool: `gmail_list_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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gmail_list_messages",
    "arguments": {}
  }
}
```

## Why gmail_list_messages is rated Low

This tool retrieves and queries existing Gmail messages without creating, modifying, or deleting any data. It is classified as Read. Severity is medium because unauthorized access to email contents could expose sensitive personal, financial, or business information, though the tool itself performs no destructive or irreversible actions.

From the tool's own definition: "Tool name 'gmail_list_messages' and description 'List Gmail messages with optional search query' indicate retrieval of email data without modification."

## Use case

AI agents call gmail_list_messages to retrieve information from Gmail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Gmail MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gmail_list_messages": {}
  }
}
```

## Other tools on Gmail MCP Server (7)

- `gmail_delete_messages` — Destructive — https://policylayer.com/tools/ampcome-mcps-gmail-mcp/gmail-delete-messages.md
- `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_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