AI agents call search_opportunities 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.
The tool retrieves opportunity data from a pipeline without creating, modifying, deleting, or executing any actions. This is a straightforward read operation with minimal risk—misuse by an AI agent would at worst expose information the agent already has access to through legitimate CRM queries.
From the tool's definition Tool name 'search_opportunities' and description 'Search GoHighLevel opportunities in a pipeline' indicate a query/retrieval operation with no side effects. Searching is explicitly listed as a Read category example in the classification rules.
Attacks that exploit this kind of access
Search GoHighLevel opportunities in a pipeline. 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_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 (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 →