Search messages with Gmail query syntax (from:, subject:, has:attachment, newer_than:7d, is:unread, etc.). ${PAGINATION_NOTE}
AI agents call gmail_search to retrieve information from Personal Gmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
gmail_search performs information retrieval only—it queries messages based on filter criteria (from, subject, attachment presence, date, read status) without creating, modifying, deleting, or executing any side effects. This is a standard read operation with minimal risk if misused (potential privacy leakage of email metadata, but no destructive or financial impact).
From the tool's definition Tool description explicitly states it "Search[es] messages" using Gmail query syntax. No modification, deletion, or execution capability is described. The operation is a query/retrieval action.
Attacks that exploit this kind of access
Search messages with Gmail query syntax (from:, subject:, has:attachment, newer_than:7d, is:unread, etc.). ${PAGINATION_NOTE}. It is categorised as a Read tool in the Personal Gmail MCP Server, which means it retrieves data without modifying state.
Register the Personal Gmail 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 Personal Gmail. 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 Personal Gmail MCP server (jaingxyz/personal-gmail-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 →