# read_message

Read a single message with full body content.

Agent View of the PolicyLayer registry record for `read_message`. HTML page: https://policylayer.com/tools/deadsimple-email/read-message

## Facts

- Tool: `read_message`
- 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": "read_message",
    "arguments": {}
  }
}
```

## Why read_message is rated Low

This tool retrieves and queries email message data without creating, modifying, deleting, or executing operations. It has no side effects beyond data retrieval. While email content may be sensitive, the read-only nature and lack of state-changing operations place it in the Read category with low severity.

From the tool's own definition: "Tool name is 'read_message' and description states 'Read a single message with full body content.' The verb 'read' and the action of retrieving message content without modification are characteristic of Read operations."

## Use case

AI agents call read_message 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": {
    "read_message": {}
  }
}
```

## 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_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_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