# update-email

Modify single email labels/status. Returns: updated message with new labelIds. Use when: marking one email read/unread/starred. For multiple: use batch-update-emails. Labels: UNREAD, STARRED, IMPORTANT, INBOX.

Agent View of the PolicyLayer registry record for `update-email`. HTML page: https://policylayer.com/tools/199-biotechnologies-mcp-google/update-email

## Facts

- Tool: `update-email`
- Server: MCP Google Workspace (`199-mcp/mcp-google`) — https://policylayer.com/tools/199-biotechnologies-mcp-google.md
- Homepage: https://github.com/199-mcp/mcp-google
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why update-email is rated Medium

This tool modifies email metadata (labels and status flags) reversibly without deleting content or executing arbitrary operations. It falls under Write rather than Read (modifies data), Execute (doesn't run code/commands), or Destructive (changes are reversible).

From the tool's own definition: "Tool description states 'Modify single email labels/status' and examples include 'marking one email read/unread/starred'. The server description confirms 'full create, read, update, and delete capabilities' with OAuth2 authentication to Gmail."

## Use case

AI agents use update-email to create or update resources in MCP Google Workspace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Google Workspace:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-email": {
      "limits": [
        {
          "counter": "update-email_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MCP Google Workspace (25)

- `delete-contact` — Destructive — https://policylayer.com/tools/199-biotechnologies-mcp-google/delete-contact.md
- `delete-email` — Destructive — https://policylayer.com/tools/199-biotechnologies-mcp-google/delete-email.md
- `delete-event` — Destructive — https://policylayer.com/tools/199-biotechnologies-mcp-google/delete-event.md
- `delete-label` — Destructive — https://policylayer.com/tools/199-biotechnologies-mcp-google/delete-label.md
- `get-contact` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/get-contact.md
- `get-email` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/get-email.md
- `get-freebusy` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/get-freebusy.md
- `list-calendars` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-calendars.md
- `list-colors` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-colors.md
- `list-contacts` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-contacts.md
- `list-emails` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-emails.md
- `list-events` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-events.md
- `list-labels` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/list-labels.md
- `search-events` — Read — https://policylayer.com/tools/199-biotechnologies-mcp-google/search-events.md
- `batch-update-emails` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/batch-update-emails.md
- `create-contact` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/create-contact.md
- `create-draft` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/create-draft.md
- `create-event` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/create-event.md
- `create-label` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/create-label.md
- `send-draft` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/send-draft.md
- `send-email` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/send-email.md
- `update-contact` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/update-contact.md
- `update-draft` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/update-draft.md
- `update-event` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/update-event.md
- `update-label` — Write — https://policylayer.com/tools/199-biotechnologies-mcp-google/update-label.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=199-biotechnologies-mcp-google · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/199-biotechnologies-mcp-google