List conversation threads from Gmail. Args: - query (string, optional): Gmail search query to filter threads - max_results (number): Maximum threads to return, 1-100 (default: 10) - label_ids (string[]): Filter by labels - page_token (string, optional): Token for pagination - response_format (
AI agents call gmail_list_threads to retrieve information from Google Workspace 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 Gmail conversation threads without creating, modifying, or deleting data. It falls squarely into the Read category. Severity is medium because email access could expose sensitive personal or business information if misused by an agent without proper consent, but the tool itself performs no destructive or system-altering actions.
From the tool's definition Tool name 'gmail_list_threads' and description 'List conversation threads from Gmail' indicate data retrieval with no modification. Arguments include query filters, pagination, and response formatting—all read-only operations.
Documented attack patterns abuse exactly the kind of access gmail_list_threads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for gmail_list_threads:
{
"version": "1",
"default": "deny",
"tools": {
"gmail_list_threads": {}
}
}gmail_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 conversation threads from Gmail. Args: - query (string, optional): Gmail search query to filter threads - max_results (number): Maximum threads to return, 1-100 (default: 10) - label_ids (string[]): Filter by labels - page_token (string, optional): Token for pagination - response_format (. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for gmail_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 Google Workspace. Nothing to install.
gmail_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 gmail_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 gmail_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.
gmail_list_threads is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, 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.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.