Low Risk

search_email_tool

Search emails with optional conversation inclusion

How to control search_email_tool ↓

What search_email_tool does on Gmail MCP Server

AI agents call search_email_tool to retrieve information from Gmail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_email_tool needs a policy

This tool queries and retrieves email data based on search criteria. It performs no creation, modification, deletion, or execution of external operations. While it accesses email content (potentially sensitive), the operation itself is non-destructive and read-only. Severity is low because search operations have minimal blast radius—an AI agent misusing this can only over-retrieve data, not alter or delete it.

From the tool's definition Tool description states 'Search emails' with optional conversation inclusion. The verb 'search' indicates data retrieval without modification. Server description confirms it 'read[s]... emails' as a read capability.

Documented attack patterns abuse exactly the kind of access search_email_tool gives an agent:

How to control search_email_tool

PolicyLayer is an MCP gateway — it sits between your AI agents and Gmail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_email_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_email_tool": {}
  }
}

search_email_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Gmail MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_email_tool

What does the search_email_tool tool do? +

Search emails with optional conversation inclusion. It is categorised as a Read tool in the Gmail MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_email_tool? +

Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for search_email_tool: 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 Gmail MCP Server. Nothing to install.

What risk level is search_email_tool? +

search_email_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_email_tool? +

Yes. Add a rate_limit block to the search_email_tool 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.

How do I block search_email_tool completely? +

Set action: deny in the PolicyLayer policy for search_email_tool. 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.

What MCP server provides search_email_tool? +

search_email_tool is provided by the Gmail MCP Server MCP server (quantum-369/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gmail MCP Server tool call.

Start from Gmail MCP Server, 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.

4 Gmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.