AI agents use send_estimate to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
The tool performs a write operation by generating and sending a business document (estimate) to a customer, which modifies CRM state. While it has business significance, it is not destructive (data is not deleted), not financial in nature (does not move money or commit financial obligations—an estimate is informational only), and not execute-level risky (it does not run arbitrary code or trigger unpredictable…
From the tool's definition Tool name is 'send_estimate' and description states 'Send an estimate to customer'. This creates a document and sends it to a customer, modifying the state of a CRM record without deleting or overwriting existing data.
Documented attack patterns abuse exactly the kind of access send_estimate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_estimate:
{
"version": "1",
"default": "deny",
"tools": {
"send_estimate": {
"limits": [
{
"counter": "send_estimate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_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.
Free to start. No card required.
Send an estimate to customer. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for send_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 GoHighLevel MCP Server. Nothing to install.
send_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 send_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 send_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.
send_estimate is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.