Read a specific email by its message ID
AI agents call gmail_read_email to retrieve information from Gmail & PostgreSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing email data based on a message ID parameter. It does not create, modify, delete, or execute anything; it only fetches email content. This is a standard Read operation with minimal risk, appropriate for an AI agent to access user's existing emails safely.
From the tool's definition Tool name contains 'read' and description states 'Read a specific email by its message ID' — retrieves email content without modification or side effects.
Attacks that exploit this kind of access
Read a specific email by its message ID. It is categorised as a Read tool in the Gmail & PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gmail & PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for gmail_read_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 & PostgreSQL MCP Server. Nothing to install.
gmail_read_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 gmail_read_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 gmail_read_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.
gmail_read_email is provided by the Gmail & PostgreSQL MCP Server MCP server (marouanemkm/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →