# delete_email

Permanently delete an email message.

Agent View of the PolicyLayer registry record for `delete_email`. HTML page: https://policylayer.com/tools/0xka13b-microsoft-mcps/delete-email

## Facts

- Tool: `delete_email`
- Server: Microsoft MCP (`0xka13b/microsoft-mcps`) — https://policylayer.com/tools/0xka13b-microsoft-mcps.md
- Homepage: https://github.com/0xka13b/microsoft-mcps
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `email_id` | string | yes | Message ID to delete |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_email",
    "arguments": {
      "email_id": "<email_id>"
    }
  }
}
```

## Why delete_email is rated Critical

This tool removes email data permanently without the ability to undo the action. Misuse by an AI agent could result in loss of important communications, evidence, or records. The word 'Permanently' confirms this is irreversible, placing it in the Destructive category rather than Write.

From the tool's own definition: "Tool name 'delete_email' combined with description 'Permanently delete an email message' explicitly indicates irreversible deletion of data."

## Use case

AI agents call delete_email to permanently remove resources in Microsoft MCP, 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 Microsoft MCP:

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

## Other tools on Microsoft MCP (13)

- `get_attachment` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-attachment.md
- `get_email` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/get-email.md
- `list_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/list-emails.md
- `me` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/me.md
- `search_emails` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/search-emails.md
- `unified_search` — Read — https://policylayer.com/tools/0xka13b-microsoft-mcps/unified-search.md
- `create_email_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-email-draft.md
- `create_reply_draft` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/create-reply-draft.md
- `move_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/move-email.md
- `reply_all_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-all-email.md
- `reply_to_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/reply-to-email.md
- `send_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/send-email.md
- `update_email` — Write — https://policylayer.com/tools/0xka13b-microsoft-mcps/update-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=0xka13b-microsoft-mcps · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xka13b-microsoft-mcps