Get the user's Gmail profile information
AI agents call get_email_profile 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.
This tool merely retrieves existing profile metadata (account settings, display name, email address, etc.) and produces no side effects. While it accesses user information, the severity is low because profile data is generally non-sensitive compared to email content, and read-only access poses minimal risk. The confidence is high given the clear 'get' verb and retrieval-only semantics.
From the tool's definition The tool 'get_email_profile' with description 'Get the user's Gmail profile information' is a read-only operation that retrieves user profile data without modification.
Attacks that exploit this kind of access
Get the user's Gmail profile information. 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 get_email_profile: 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.
get_email_profile 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 get_email_profile 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 get_email_profile. 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.
get_email_profile is provided by the Gmail MCP Server MCP server (xiangwanggithub/gmail-mcp). 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 →