This record as markdown: /tools/ghl/generate-estimate-number.md
What generate_estimate_number does on Ghl
AI agents use generate_estimate_number 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 |
Parameters from the server's own tool schema.
Why generate_estimate_number is rated Medium
This tool creates and allocates new data (an estimate number) that persists in the GoHighLevel system. While not destructive and lacking financial impact by itself, it writes/creates a new record.
From the tool's definition 'Generate a unique estimate number' – creates a new unique identifier/record in the system, modifying state by allocating a new estimate number.
Attacks that exploit this kind of access
The rule that runs generate_estimate_number 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 generate_estimate_number, this is the rule to start with:
generate_estimate_number 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 generate_estimate_number call is checked against it from then on.
Questions about generate_estimate_number
Generate a unique estimate number. 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.
generate_estimate_number accepts 1 parameter: altId. 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 generate_estimate_number: 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.
generate_estimate_number 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 generate_estimate_number 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 generate_estimate_number. 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.
generate_estimate_number 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