list_threads

List conversation threads, optionally scoped to an inbox.

SERVERAgenticEmail SOURCEhttps://api.agenticemail.dev/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/dev-agenticemail-mcp/list-threads.md

WHAT IT DOES

What list_threads does on AgenticEmail

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.

Parameter	Type	Required	Description
`inbox_id`	string	—

Parameters from the server's own tool schema.

RISK

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 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_threads safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AgenticEmail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_threads, this is the rule to start with:

list_threads Allowed

list_threads is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_threads": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AgenticEmail, apply this rule, and every list_threads call is checked against it from then on.

FAQ

Questions about list_threads

What does the list_threads tool do? +

List conversation threads, optionally scoped to an inbox. It is categorised as a Read tool in the AgenticEmail MCP Server, which means it retrieves data without modifying state.

What parameters does list_threads accept? +

list_threads accepts 1 parameter: inbox_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_threads? +

Register the AgenticEmail MCP server in PolicyLayer and add a rule for list_threads: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AgenticEmail. Nothing to install.

What risk level is list_threads? +

list_threads is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_threads? +

Yes. Add a rate_limit block to the list_threads rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_threads completely? +

Set action: deny in the PolicyLayer policy for list_threads. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_threads? +

list_threads is provided by the AgenticEmail MCP server (https://api.agenticemail.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AgenticEmail, and thousands of servers like it.

This server

All 9 AgenticEmail tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →