list_estimates

List all estimates

SERVERGhl SOURCEghl-mcp-server

Low RISK CLASS

Category Read

Parameters 62 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/list-estimates.md

WHAT IT DOES

What list_estimates does on Ghl

AI agents call list_estimates to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`altId`	string	—	Location ID
`limit`	string	Yes	Number of results per page
`offset`	string	Yes	Offset for pagination
`search`	string	—	Search term
`status`	string	—	Filter by status
`contactId`	string	—	Filter by contact ID

Parameters from the server's own tool schema.

RISK

Why list_estimates is rated Low

This tool queries and returns estimate data without side effects. It is a straightforward read operation that retrieves existing information. Given the CRM context (GoHighLevel), the blast radius of misuse is minimal — an agent could over-query or exfiltrate estimate records, but cannot modify or delete them.

From the tool's definition Tool name is 'list_estimates' and description states 'List all estimates' — a retrieval operation with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_estimates 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 list_estimates, this is the rule to start with:

list_estimates Allowed

list_estimates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_estimates": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every list_estimates call is checked against it from then on.

FAQ

Questions about list_estimates

What does the list_estimates tool do? +

List all estimates. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does list_estimates accept? +

list_estimates accepts 6 parameters: altId, limit, offset, search, status, contactId. Required: limit, offset. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_estimates? +

Register the Ghl MCP server in PolicyLayer and add a rule for list_estimates: 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 list_estimates? +

list_estimates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_estimates? +

Yes. Add a rate_limit block to the list_estimates 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 list_estimates completely? +

Set action: deny in the PolicyLayer policy for list_estimates. 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 list_estimates? +

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

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 253 Ghl tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →