email_search

Search emails in a connected mailbox. Requires an active email integration.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/email-search.md

WHAT IT DOES

What email_search does on FlowDot MCP Server

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

RISK

Why email_search is rated Low

This tool retrieves and queries email data without creating, modifying, or deleting messages. However, the severity is medium rather than low because email often contains sensitive personal and business information (credentials, financial details, PII), and unauthorized search access could expose significant data. The tool requires an active email integration, implying it operates on user email accounts.

From the tool's definition Tool name 'email_search' and description 'Search emails in a connected mailbox' indicate a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_search, this is the rule to start with:

email_search Allowed

email_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "email_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every email_search call is checked against it from then on.

FAQ

Questions about email_search

What does the email_search tool do? +

Search emails in a connected mailbox. Requires an active email integration. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on email_search? +

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

What risk level is email_search? +

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

Can I rate-limit email_search? +

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

How do I block email_search completely? +

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

What MCP server provides email_search? +

email_search is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →