search_directory
A read tool on the MCP Google Contacts MCP server.
This record as markdown: /tools/4tal-mcp-google-contacts/search-directory.md
What search_directory does on MCP Google Contacts Server
AI agents call search_directory to retrieve information from MCP Google Contacts Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_directory is rated Low
Search functions query and retrieve data (contacts and directory information) without modifying, deleting, or executing external operations. This is a Read operation. Severity is medium rather than low because search on Google Workspace directories could expose organizational structure, employee contact details, or sensitive contact information if an agent misuses it or is manipulated into returning unauthorized…
From the tool's definition Tool name 'search_directory' indicates a search operation, and the server description mentions 'searching' contacts and 'accessing Google Workspace directories.' The empty description limits confidence, but search operations typically retrieve data without…
Attacks that exploit this kind of access
The rule that runs search_directory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Contacts Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_directory, this is the rule to start with:
search_directory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Contacts Server, apply this rule, and every search_directory call is checked against it from then on.
Questions about search_directory
search_directory is a read tool on the MCP Google Contacts Server MCP server. 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_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 MCP Google Contacts Server. Nothing to install.
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 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 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.
search_directory is provided by the MCP Google Contacts Server MCP server (4tal/mcp-google-contacts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Contacts Server, and thousands of servers like it.
This server
Across the catalogue