Search contacts by name, email, or phone number.
AI agents call search_contacts to retrieve information from MCP Google Contacts Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches existing contact data without creating, modifying, or deleting records. The operation is read-only with no side effects. The severity is low because search results expose contact information but cannot be misused to cause data loss or financial harm in isolation.
From the tool's definition Tool name 'search_contacts' and description 'Search contacts by name, email, or phone number' indicate a query operation with no modification capability.
Documented attack patterns abuse exactly the kind of access search_contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Contacts Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_contacts:
{
"version": "1",
"default": "deny",
"tools": {
"search_contacts": {}
}
}search_contacts 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 contacts by name, email, or phone number. It is categorised as a Read tool in the MCP Google Contacts Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Contacts Server MCP server in PolicyLayer and add a rule for search_contacts: 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 MCP Google Contacts Server. Nothing to install.
search_contacts 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 search_contacts 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 search_contacts. 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.
search_contacts is provided by the MCP Google Contacts Server MCP server (rayanzaki/mcp-google-contacts-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 MCP Google Contacts Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 MCP Google Contacts Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.