Search Gmail threads matching a query.
AI agents call search_threads to retrieve information from Google Workspace Mcp Sidecar 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 thread data based on search criteria. It performs a read-only operation with no side effects—it neither creates, modifies, deletes, nor executes external operations. The 'search' verb and 'query' language clearly position this as a retrieval operation. While email content can be sensitive, the tool itself is non-destructive and read-only, making it a low-severity Read category.
From the tool's definition Tool name 'search_threads' and description 'Search Gmail threads matching a query' indicate a search/query operation with no modification or deletion of data.
Attacks that exploit this kind of access
Search Gmail threads matching a query. It is categorised as a Read tool in the Google Workspace Mcp Sidecar MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace Mcp Sidecar MCP server in PolicyLayer and add a rule for search_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 Mcp Sidecar. Nothing to install.
search_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 search_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 search_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.
search_threads is provided by the Google Workspace Mcp Sidecar MCP server (milad/google-mcp-sidecar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →