# get_verification_code

A read tool on the Pypi:deadsimple Email MCP server.

Agent View of the PolicyLayer registry record for `get_verification_code`. HTML page: https://policylayer.com/tools/deadsimple-email/get-verification-code

## Facts

- Tool: `get_verification_code`
- 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: Read (Low risk)
- Registry record: grade D, 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": "get_verification_code",
    "arguments": {}
  }
}
```

## Why get_verification_code is rated Low

The tool retrieves verification codes from email messages—a read-only operation with no side effects on the email system or external state. Even though the tool description is empty, the name pattern and server purpose (extracting codes from mail) classify this as a Read operation.

From the tool's own definition: "Tool name 'get_verification_code' and sibling tools include 'get_verification_link' and 'read_message'/'read_messages', indicating this retrieves verification codes from inbound mail without modifying data."

## Use case

AI agents call get_verification_code to retrieve information from Pypi:deadsimple Email 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 Pypi:deadsimple Email:

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

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

- `delete_inbox` — Destructive — https://policylayer.com/tools/deadsimple-email/delete-inbox.md
- `get_usage` — Read — https://policylayer.com/tools/deadsimple-email/get-usage.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