Get the authenticated user's Gmail profile information.
AI agents call get_gmail_profile to retrieve information from Google Connections without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves profile metadata for the authenticated user only. It is a read-only operation that queries Gmail service configuration without side effects. The blast radius is minimal—profile information typically includes basic account metadata (email address, display name, settings) that, while potentially sensitive, does not enable unauthorized actions or data modification.
From the tool's definition Tool name 'get_gmail_profile' and description 'Get the authenticated user's Gmail profile information' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get the authenticated user's Gmail profile information. It is categorised as a Read tool in the Google Connections MCP Server, which means it retrieves data without modifying state.
Register the Google Connections MCP server in PolicyLayer and add a rule for get_gmail_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 Google Connections. Nothing to install.
get_gmail_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_gmail_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_gmail_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_gmail_profile is provided by the Google Connections MCP server (michaelzrork/google-connections-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 →