AI agents call get_account_info to retrieve information from Gg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about the authenticated account (specifically the email address). It performs a query operation without modifying, deleting, executing code, or committing financial transactions. The blast radius of misuse is minimal—an agent could only learn the account's email address, which is typically non-sensitive metadata and is often already known or visible in the application context.
From the tool's definition Tool name 'get_account_info' and description 'Get the email address of the currently authenticated Google account' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the email address of the currently authenticated Google account. It is categorised as a Read tool in the Gg MCP Server, which means it retrieves data without modifying state.
Register the Gg MCP server in PolicyLayer and add a rule for get_account_info: 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 Gg. Nothing to install.
get_account_info 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_account_info 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_account_info. 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_account_info is provided by the Gg MCP server (tannht/google-cloud-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 →