Search Gmail messages using Gmail query syntax. Use this to find emails by sender, subject, label, date, or read status. Returns message IDs, subjects, snippets, and thread IDs for use with gmail_thread.
AI agents call gmail_search to retrieve information from Access 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 data without creating, modifying, deleting, or executing operations. However, it accesses sensitive personal communication data (emails), which could expose PII, credentials, or confidential information if an AI agent is compromised or misuses it.
From the tool's definition Tool description states it "Search[es] Gmail messages" and "Returns message IDs, subjects, snippets, and thread IDs" - purely data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Search Gmail messages using Gmail query syntax. Use this to find emails by sender, subject, label, date, or read status. Returns message IDs, subjects, snippets, and thread IDs for use with gmail_thread. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for gmail_search: 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 Access. Nothing to install.
gmail_search 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_search 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_search. 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_search is provided by the Access MCP server (scottpedia0/access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
gmail_search is one line of Access's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →