Search for contacts by name, email, or phone number.
AI agents call contacts_searchContacts to retrieve information from Google MCP Remote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation on contact data. It queries existing contacts but does not create, modify, delete, or trigger external actions. The blast radius of misuse is limited to unauthorized disclosure of contact information, which is a confidentiality concern but not as severe as destructive or financial impacts. Classified as Read/low severity.
From the tool's definition Tool name 'contacts_searchContacts' and description 'Search for contacts by name, email, or phone number' indicate a query operation that retrieves contact information without modifying, deleting, or executing side effects.
Documented attack patterns abuse exactly the kind of access contacts_searchContacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for contacts_searchContacts:
{
"version": "1",
"default": "deny",
"tools": {
"contacts_searchContacts": {}
}
}contacts_searchContacts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for contacts by name, email, or phone number. It is categorised as a Read tool in the Google MCP Remote MCP Server, which means it retrieves data without modifying state.
Register the Google MCP Remote MCP server in PolicyLayer and add a rule for contacts_searchContacts: 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 MCP Remote. Nothing to install.
contacts_searchContacts 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_searchContacts 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_searchContacts. 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_searchContacts is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP Remote, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Google MCP Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.