# mark-as-unread

Mark emails as unread

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

## Facts

- Tool: `mark-as-unread`
- 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: Write (Medium risk)
- Registry record: grade D, 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": "mark-as-unread",
    "arguments": {}
  }
}
```

## Why mark-as-unread is rated Medium

The tool modifies email metadata (read/unread status) without deleting data or executing arbitrary code. It is reversible and has minimal blast radius. Even if an AI agent misused this tool, users could easily correct the state. This is a Write-category risk, not Read (because it changes state), not Execute (no code execution), not Destructive (fully reversible), and not Financial (no money involved).

From the tool's own definition: "Tool name 'mark-as-unread' and description 'Mark emails as unread' indicate a state modification operation on email messages. This is a reversible write operation—the action can be undone by marking the email as read again."

## Use case

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

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark-as-unread": {
      "limits": [
        {
          "counter": "mark-as-unread_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Meme MCP Server (16)

- `move-to-trash` — Destructive — https://policylayer.com/tools/0x8687-mcp-gmail-v1/move-to-trash.md
- `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
- `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