search_opportunities

Search for opportunities in GoHighLevel CRM using various filters like pipeline, stage, contact, status, etc.

Server GoHighLevel MCP Server thinkbedo/gohighlevel_mcp
Category Read
Risk class Low
Parameters 00 required

What search_opportunities does on GoHighLevel MCP Server

AI agents call search_opportunities 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.

Why search_opportunities needs a policy

This tool retrieves or queries opportunity data from the CRM using filters (pipeline, stage, contact, status). It has no side effects—it does not create, modify, delete, or execute external operations. It is a straightforward Read operation with minimal security risk, as it only exposes existing data subject to the user's existing CRM access controls.

From the tool's definition Tool name 'search_opportunities' and description stating it 'Search for opportunities in GoHighLevel CRM using various filters' indicates a query/retrieval operation with no modification or deletion of data.

Questions about search_opportunities

What does the search_opportunities tool do? +

Search for opportunities in GoHighLevel CRM using various filters like pipeline, stage, contact, status, etc. 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_opportunities? +

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

What risk level is search_opportunities? +

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

Can I rate-limit search_opportunities? +

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.

How do I block search_opportunities completely? +

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.

What MCP server provides search_opportunities? +

search_opportunities is provided by the GoHighLevel MCP Server MCP server (thinkbedo/gohighlevel_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.