email_read

Read a specific email message by ID. Returns full message content including headers, body, and attachments list.

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-read.md

WHAT IT DOES

What email_read does on FlowDot MCP Server

AI agents call email_read 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_read is rated Low

This tool retrieves and queries email message content. While it does not modify data, emails often contain sensitive personal, financial, or business information. The medium severity reflects the potential for information disclosure if an AI agent accesses emails without proper authorization, though the tool itself performs no destructive or state-changing operations.

From the tool's definition Tool name 'email_read' and description 'Read a specific email message by ID. Returns full message content including headers, body, and attachments list.' indicate retrieval of data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_read 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_read, this is the rule to start with:

email_read Allowed

email_read 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_read": {}
  }
}

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_read call is checked against it from then on.

FAQ

Questions about email_read

What does the email_read tool do? +

Read a specific email message by ID. Returns full message content including headers, body, and attachments list. 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_read? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for email_read: 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_read? +

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

Can I rate-limit email_read? +

Yes. Add a rate_limit block to the email_read 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_read completely? +

Set action: deny in the PolicyLayer policy for email_read. 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_read? +

email_read 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

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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