# delete_inbox

Delete an inbox and all its messages.

Agent View of the PolicyLayer registry record for `delete_inbox`. HTML page: https://policylayer.com/tools/deadsimple-email/delete-inbox

## Facts

- Tool: `delete_inbox`
- Server: Pypi:deadsimple Email (`pypi:deadsimple-email`) — https://policylayer.com/tools/deadsimple-email.md
- Install: `npx -y pypi:deadsimple-email`
- Homepage: https://github.com/deadsimple-email/deadsimple-email
- Risk category: Destructive (Critical risk)
- Registry record: grade D, 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": "delete_inbox",
    "arguments": {}
  }
}
```

## Why delete_inbox is rated Critical

This tool irreversibly deletes an entire inbox and all associated messages—a classic destructive action that cannot be undone. The blast radius is high because an AI agent with access could permanently lose email data, verification codes, and other critical communications.

From the tool's own definition: "delete_inbox: Delete an inbox and all its messages"

## Use case

AI agents call delete_inbox to permanently remove resources in Pypi:deadsimple Email, 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 Pypi:deadsimple Email:

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

## Other tools on Pypi:deadsimple Email (13)

- `get_usage` — Read — https://policylayer.com/tools/deadsimple-email/get-usage.md
- `get_verification_code` — Read — https://policylayer.com/tools/deadsimple-email/get-verification-code.md
- `get_verification_link` — Read — https://policylayer.com/tools/deadsimple-email/get-verification-link.md
- `list_inboxes` — Read — https://policylayer.com/tools/deadsimple-email/list-inboxes.md
- `list_threads` — Read — https://policylayer.com/tools/deadsimple-email/list-threads.md
- `read_message` — Read — https://policylayer.com/tools/deadsimple-email/read-message.md
- `read_messages` — Read — https://policylayer.com/tools/deadsimple-email/read-messages.md
- `read_thread` — Read — https://policylayer.com/tools/deadsimple-email/read-thread.md
- `wait_for_email` — Read — https://policylayer.com/tools/deadsimple-email/wait-for-email.md
- `create_inbox` — Write — https://policylayer.com/tools/deadsimple-email/create-inbox.md
- `forward_message` — Write — https://policylayer.com/tools/deadsimple-email/forward-message.md
- `reply_to_message` — Write — https://policylayer.com/tools/deadsimple-email/reply-to-message.md
- `send_email` — Write — https://policylayer.com/tools/deadsimple-email/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=deadsimple-email · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deadsimple-email