Search Gmail using Gmail search syntax. Returns matching messages with snippets.
AI agents call searchGmail to retrieve information from Google Workspace MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
searchGmail retrieves and queries Gmail messages without modifying, deleting, or executing any operations. It is a pure read operation that returns data matching search criteria. Low severity because the blast radius of misuse is limited to information disclosure within the user's own mailbox.
From the tool's definition Tool description states 'Search Gmail using Gmail search syntax. Returns matching messages with snippets.' - search and return operations are read-only with no modification or deletion of data.
Attacks that exploit this kind of access
Search Gmail using Gmail search syntax. Returns matching messages with snippets. It is categorised as a Read tool in the Google Workspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for searchGmail: 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 Server. Nothing to install.
searchGmail 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 searchGmail 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 searchGmail. 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.
searchGmail is provided by the Google Workspace MCP Server MCP server (pm990320/google-workspace-mcp). 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 →