# get_message

Get a single message by id, including attachment metadata. Use read_attachment to read attachment contents.

Agent View of the PolicyLayer registry record for `get_message`. HTML page: https://policylayer.com/tools/dev-agenticemail-mcp/get-message

## Facts

- Tool: `get_message`
- Server: AgenticEmail (`https://api.agenticemail.dev/mcp`) — https://policylayer.com/tools/dev-agenticemail-mcp.md
- Homepage: https://github.com/https://api.agenticemail.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server auth posture: gated
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `inbox_id` | string | yes |  |
| `message_id` | string | yes |  |

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": "get_message",
    "arguments": {
      "inbox_id": "<inbox_id>",
      "message_id": "<message_id>"
    }
  }
}
```

## Why get_message is rated Low

This tool queries and retrieves email message data without creating, modifying, or deleting content. However, 'medium' severity reflects that email messages may contain sensitive personal, financial, or authentication information (passwords, tokens, PII), creating moderate blast radius if an AI agent retrieves unauthorized messages. Confidence is high because the description explicitly states retrieval behavior.

From the tool's own definition: "Tool retrieves 'a single message by id, including attachment metadata' with no modification or deletion capability—core Read operation. Related tools (read_attachment, list_messages, list_threads) confirm the Read-only pattern of this server."

## Use case

AI agents call get_message to retrieve information from AgenticEmail 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 AgenticEmail:

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

## Other tools on AgenticEmail (8)

- `get_thread` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/get-thread.md
- `list_inboxes` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-inboxes.md
- `list_messages` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-messages.md
- `list_threads` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-threads.md
- `read_attachment` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/read-attachment.md
- `create_inbox` — Write — https://policylayer.com/tools/dev-agenticemail-mcp/create-inbox.md
- `reply_to_message` — Write — https://policylayer.com/tools/dev-agenticemail-mcp/reply-to-message.md
- `send_message` — Write — https://policylayer.com/tools/dev-agenticemail-mcp/send-message.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=dev-agenticemail-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agenticemail-mcp