# list_messages

List recent messages in an inbox.

Agent View of the PolicyLayer registry record for `list_messages`. HTML page: https://policylayer.com/tools/dev-agenticemail-mcp/list-messages

## Facts

- Tool: `list_messages`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `inbox_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": "list_messages",
    "arguments": {
      "inbox_id": "<inbox_id>"
    }
  }
}
```

## Why list_messages is rated Low

This tool retrieves or queries existing messages from an inbox without creating, modifying, deleting, or executing any operations. It has no capability to alter data or trigger external actions. The blast radius of misuse is minimal—an agent could retrieve messages it shouldn't see, but cannot modify them or cause broader harm.

From the tool's own definition: "Tool name 'list_messages' and description 'List recent messages in an inbox' indicate a retrieval operation with no side effects. The verb 'list' is explicitly called out in the classification rules as a Read action."

## Use case

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

## Other tools on AgenticEmail (8)

- `get_message` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/get-message.md
- `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_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