generate_estimate_number

Generate a unique estimate number

SERVERGhl SOURCEghl-mcp-server
Medium RISK CLASS
Category Write
Parameters 10 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about generate_estimate_number

What does the generate_estimate_number tool do? +

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.

What parameters does generate_estimate_number accept? +

generate_estimate_number accepts 1 parameter: altId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on generate_estimate_number? +

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.

What risk level is generate_estimate_number? +

generate_estimate_number is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_estimate_number? +

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.

How do I block generate_estimate_number completely? +

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.

What MCP server provides generate_estimate_number? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.