This record as markdown: /tools/aiwerk-mcp-server-ghl/opportunities-search-opportunity.md
What opportunities_search_opportunity does on Ghl
AI agents call opportunities_search_opportunity 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 |
|---|---|---|---|
q | string | — | |
id | string | — | Opportunity Id |
date | string | — | Start date |
page | number | — | |
limit | number | — | Limit Per Page records count. will allow maximum up to 100 and default will be 20 |
order | string | — | |
status | string | — | |
country | string | — | |
endDate | string | — | End date |
getNotes | boolean | — | get Notes in contact |
getTasks | boolean | — | get Tasks in contact |
campaignId | string | — | Campaign Id |
Parameters from the server's own tool schema.
Why opportunities_search_opportunity is rated Low
Even though opportunities_search_opportunity only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs opportunities_search_opportunity 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 opportunities_search_opportunity, this is the rule to start with:
opportunities_search_opportunity 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 opportunities_search_opportunity call is checked against it from then on.
Questions about opportunities_search_opportunity
Search Opportunity. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
opportunities_search_opportunity accepts 12 parameters: q, id, date, page, limit, order, status, country, endDate, getNotes, getTasks, campaignId. 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 opportunities_search_opportunity: 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.
opportunities_search_opportunity 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 opportunities_search_opportunity 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 opportunities_search_opportunity. 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.
opportunities_search_opportunity is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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