update_opportunity
Update an existing opportunity with new details (full update)
This record as markdown: /tools/ghl/update-opportunity.md
What update_opportunity does on Ghl
AI agents use update_opportunity to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Updated name/title of the opportunity |
status | string | — | Updated status of the opportunity |
assignedTo | string | — | Updated assigned user ID |
pipelineId | string | — | Updated pipeline ID |
monetaryValue | number | — | Updated monetary value in dollars |
opportunityId | string | Yes | The unique ID of the opportunity to update |
pipelineStageId | string | — | Updated pipeline stage ID |
Parameters from the server's own tool schema.
Why update_opportunity is rated Medium
This tool modifies existing opportunity records within the GoHighLevel CRM system. It is a Write operation because it creates or modifies data reversibly—opportunities can be updated again or reverted. The severity is high because a malicious AI agent could arbitrarily alter sales opportunities, customer pipeline data, or deal terms, causing business disruption.
From the tool's definition Tool name is 'update_opportunity' and description states 'Update an existing opportunity with new details (full update)'. The word 'Update' and 'full update' indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_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 update_opportunity, this is the rule to start with:
update_opportunity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_opportunity call is checked against it from then on.
Questions about update_opportunity
Update an existing opportunity with new details (full update). It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_opportunity accepts 7 parameters: name, status, assignedTo, pipelineId, monetaryValue, opportunityId, pipelineStageId. Required: opportunityId. 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 update_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.
update_opportunity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_opportunity 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