get-email

SERVERMCP Google Workspace SOURCE199-mcp/mcp-google

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/199-biotechnologies-mcp-google/get-email.md

WHAT IT DOES

What get-email does on MCP Google Workspace

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

RISK

Why get-email is rated Low

This tool performs a straightforward data retrieval operation on an existing email message. It has no side effects—it only reads and returns email content without creating, modifying, deleting, or executing any operations. The severity is low because misuse would only expose the user's own email data to the AI agent, not cause irreversible damage or financial impact.

From the tool's definition Tool name 'get-email' and description states 'Retrieve one email by messageId' with 'Returns: full message with headers, body (plain/html), attachments metadata.' The description explicitly uses 'reading email content' terminology and contains no mention of…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get-email safely

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

get-email Allowed

get-email 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": {
    "get-email": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every get-email call is checked against it from then on.

FAQ

Questions about get-email

What does the get-email tool do? +

Retrieve one email by messageId. Returns: full message with headers, body (plain/html), attachments metadata. Use when: reading email content after list-emails. Note: messageId from list-emails required. It is categorised as a Read tool in the MCP Google Workspace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-email? +

Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for get-email: 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 MCP Google Workspace. Nothing to install.

What risk level is get-email? +

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

Can I rate-limit get-email? +

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

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

get-email is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Google Workspace, and thousands of servers like it.

This server

All 26 MCP Google Workspace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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