AI agents call contacts_resolve_email to retrieve information from Google without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup/query operation, resolving a contact name to an email address. It retrieves existing contact information without modifying, creating, or deleting any data. The blast radius is low as it only reads contact data.
From the tool's definition Resolve a contact name to email address
Attacks that exploit this kind of access
Resolve a contact name to email address. It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for contacts_resolve_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 Google. Nothing to install.
contacts_resolve_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 contacts_resolve_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 contacts_resolve_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.
contacts_resolve_email is provided by the Google MCP server (robcerda/google-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 →