search_opportunities
Search for opportunities in GoHighLevel CRM using various filters like pipeline, stage, contact, status, etc.
This record as markdown: /tools/ghl/search-opportunities.md
What search_opportunities does on Ghl
AI agents call search_opportunities to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of opportunities to return (default: 20, max: 100) |
query | string | — | General search query (searches name, contact info) |
status | string | — | Filter by opportunity status |
contactId | string | — | Filter by specific contact ID |
assignedTo | string | — | Filter by assigned user ID |
pipelineId | string | — | Filter by specific pipeline ID |
pipelineStageId | string | — | Filter by specific pipeline stage ID |
Parameters from the server's own tool schema.
Why search_opportunities is rated Low
The tool queries/searches existing opportunity records using filters. It retrieves information without creating, modifying, or deleting data. This is a standard read operation with minimal blast radius if misused by an AI agent — worst case, an agent queries for opportunities it shouldn't have access to, which is an access control issue rather than a data integrity or financial risk.
From the tool's definition Tool name 'search_opportunities' and description states it 'Search for opportunities in GoHighLevel CRM using various filters' — a retrieval operation with no modification or deletion of data.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs search_opportunities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_opportunities, this is the rule to start with:
search_opportunities 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 Ghl, apply this rule, and every search_opportunities call is checked against it from then on.
Questions about search_opportunities
Search for opportunities in GoHighLevel CRM using various filters like pipeline, stage, contact, status, etc. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
search_opportunities accepts 7 parameters: limit, query, status, contactId, assignedTo, pipelineId, pipelineStageId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for search_opportunities: 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_opportunities 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_opportunities 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_opportunities. 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_opportunities is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue