AI agents call open-email 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.
Opening an email in a browser is a read/view action; it retrieves and displays the email content without modifying, deleting, or sending anything. Severity is low as it only exposes email content visually. Confidence is slightly reduced because 'open' could theoretically trigger read-receipt marking, but the primary action is display/read.
From the tool's definition "Open email in browser" — retrieves/displays an email in the browser interface
Documented attack patterns abuse exactly the kind of access open-email gives an agent:
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 open-email:
{
"version": "1",
"default": "deny",
"tools": {
"open-email": {}
}
}open-email is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open email in browser. It is categorised as a Read tool in the Gmail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for open-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 Gmail MCP Server. Nothing to install.
open-email 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 open-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.
Set action: deny in the PolicyLayer policy for open-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.
open-email is provided by the Gmail MCP Server MCP server (jasonsum/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
6 Gmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.