List email threads matching a query. Returns thread summaries with participant lists. For broad queries, use a high max_results (100-200) and paginate with nextPageToken for complete results.
AI agents call list_threads to retrieve information from AgentCloak without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries email thread data without modifying, deleting, or executing any operations. It returns summaries and metadata only. The read-only architecture of AgentCloak and explicit PII redaction measures further confirm this is a passive information retrieval tool with minimal risk. The pagination guidance ('paginate with nextPageToken') is typical for safe list operations.
From the tool's definition Tool name 'list_threads' and description 'List email threads matching a query. Returns thread summaries with participant lists' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access list_threads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AgentCloak, and nothing reaches the server without passing your rules. This is the rule we recommend for list_threads:
{
"version": "1",
"default": "deny",
"tools": {
"list_threads": {}
}
}list_threads is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List email threads matching a query. Returns thread summaries with participant lists. For broad queries, use a high max_results (100-200) and paginate with nextPageToken for complete results. It is categorised as a Read tool in the AgentCloak MCP Server, which means it retrieves data without modifying state.
Register the AgentCloak 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 AgentCloak. Nothing to install.
list_threads is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
list_threads is provided by the AgentCloak MCP server (ryanfren/agentcloak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AgentCloak, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 AgentCloak tools catalogued and risk-classified — across an index of 43,000+ MCP servers.