list_threads

List conversation threads in an inbox.

SERVERPypi:deadsimple Email SOURCEpypi:deadsimple-email

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deadsimple-email/list-threads.md

WHAT IT DOES

What list_threads does on Pypi:deadsimple Email

AI agents call list_threads 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.

RISK

Why list_threads is rated Low

This tool queries and returns data about conversation threads without creating, modifying, deleting, or executing any operations. It is a straightforward read operation. Severity is low because listing threads does not grant access to message content itself (separate tools like read_message handle that) and poses minimal risk even if misused by an agent.

From the tool's definition Tool name is 'list_threads' and description states 'List conversation threads in an inbox' — a pure retrieval operation with no modification or side effects.

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 Pypi:deadsimple Email, 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 Pypi:deadsimple Email, 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 in an inbox. It is categorised as a Read tool in the Pypi:deadsimple Email MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_threads? +

Register the Pypi:deadsimple Email 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 Pypi:deadsimple Email. 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 Pypi:deadsimple Email MCP server (pypi:deadsimple-email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pypi:deadsimple Email, and thousands of servers like it.

This server

All 14 Pypi:deadsimple Email 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 →