# list_threads

List conversation threads, optionally scoped to an inbox.

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

## Facts

- Tool: `list_threads`
- 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
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `inbox_id` | string | no |  |

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

## Why list_threads is rated Low

This tool queries and returns conversation threads without creating, modifying, deleting, or executing any side effects. It is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's own definition: "Tool name 'list_threads' and description 'List conversation threads, optionally scoped to an inbox' indicate a retrieval operation with no modification or deletion of data."

## Use case

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

## 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_messages` — Read — https://policylayer.com/tools/dev-agenticemail-mcp/list-messages.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