This record as markdown: /tools/ghl/create-opportunity.md
What create_opportunity does on Ghl
AI agents use create_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 | Yes | Name/title of the opportunity |
status | string | — | Initial status of the opportunity (default: open) |
contactId | string | Yes | ID of the contact associated with this opportunity |
assignedTo | string | — | User ID to assign this opportunity to |
pipelineId | string | Yes | ID of the pipeline this opportunity belongs to |
monetaryValue | number | — | Monetary value of the opportunity in dollars |
Parameters from the server's own tool schema.
Why create_opportunity is rated Medium
This tool creates new records (opportunities) in a CRM database, which is a reversible write operation. While it modifies business data and could have downstream effects on sales workflows and reporting, it does not delete, destroy, or move money.
From the tool's definition Tool name 'create_opportunity' and description 'Create a new opportunity in GoHighLevel CRM' indicate creation of new data in a CRM system.
Attacks that exploit this kind of access
The rule that runs create_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 create_opportunity, this is the rule to start with:
create_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 create_opportunity call is checked against it from then on.
Questions about create_opportunity
Create a new opportunity in GoHighLevel CRM. 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.
create_opportunity accepts 6 parameters: name, status, contactId, assignedTo, pipelineId, monetaryValue. Required: name, contactId, pipelineId. 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 create_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.
create_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 create_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 create_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.
create_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