This record as markdown: /tools/ghl/create-estimate.md
What create_estimate does on Ghl
AI agents use create_estimate 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 |
|---|---|---|---|
altId | string | — | Location ID |
title | string | Yes | Estimate title |
currency | string | — | Currency code |
contactId | string | Yes | Contact ID |
issueDate | string | — | Issue date |
validUntil | string | — | Valid until date |
Parameters from the server's own tool schema.
Why create_estimate is rated Medium
This tool creates new estimate records, which is a reversible write operation. While estimates are financial in nature, the tool itself does not move money or commit financial obligations—it only generates a document.
From the tool's definition Tool name 'create_estimate' and description 'Create a new estimate' indicate creation of new data/documents. GoHighLevel is a CRM/business platform where estimates are financial documents that typically convert to invoices/orders.
Attacks that exploit this kind of access
The rule that runs create_estimate 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_estimate, this is the rule to start with:
create_estimate 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_estimate call is checked against it from then on.
Questions about create_estimate
Create a new estimate. 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_estimate accepts 6 parameters: altId, title, currency, contactId, issueDate, validUntil. Required: title, contactId. 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_estimate: 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_estimate 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_estimate 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_estimate. 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_estimate 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