AI agents call contacts_search_directory 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 retrieves organizational contact/directory information without creating, modifying, or deleting data. It is a read-only query operation. Severity is medium (not low) because it could expose sensitive directory information (employee names, emails, organizational structure) if misused by a malicious agent, but the blast radius is limited to information disclosure rather than data destruction or financial…
From the tool's definition Tool name includes 'search' and description states 'Search organization directory' — both indicate data retrieval with no modification or deletion. The operation queries existing directory information without side effects.
Attacks that exploit this kind of access
Search organization directory (Google Workspace accounts only). 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_search_directory: 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_search_directory 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_search_directory 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_search_directory. 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_search_directory 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 →