AI agents call search_contacts to retrieve information from Ghl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact data based on search criteria without side effects. It matches the Read category definition: queries data with no side effects. Severity is low because search results expose contact information but do not enable financial transactions, code execution, or data destruction.
From the tool's definition Tool name is 'search_contacts' and description states it 'Search for GoHighLevel contacts by name, email, phone, tag, or advanced filters' — purely a query/search operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Search for GoHighLevel contacts by name, email, phone, tag, or advanced filters. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
Register the Ghl 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 Ghl. 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 Ghl MCP server (snack-jpg/ghl-mcp). 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 →