Low Risk

search_contacts

Search contacts in a location

How to control search_contacts ↓

What search_contacts does on GoHighLevel MCP Server

AI agents call search_contacts to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_contacts needs a policy

The tool performs a search/query operation to retrieve contact information. Search operations are classified as Read-category tools as they retrieve data without creating, modifying, deleting, or executing external operations. The limited blast radius of a mistaken search query (user sees unintended contact results) justifies low severity.

From the tool's definition Tool name 'search_contacts' and description 'Search contacts in a location' indicate a query operation that retrieves contact data without modification or side effects.

Documented attack patterns abuse exactly the kind of access search_contacts gives an agent:

How to control search_contacts

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_contacts:

policy.json
{
  "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.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_contacts

What does the search_contacts tool do? +

Search contacts in a location. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_contacts? +

Register the GoHighLevel MCP 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 GoHighLevel MCP Server. Nothing to install.

What risk level is search_contacts? +

search_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_contacts? +

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.

How do I block search_contacts completely? +

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.

What MCP server provides search_contacts? +

search_contacts is provided by the GoHighLevel MCP Server MCP server (basicmachines-co/open-ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GoHighLevel MCP Server tool call.

Start from GoHighLevel MCP Server, 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.

64 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.