New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update-estimate

Update an existing estimate with new details

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/update-estimate.md

What update-estimate does on GoHighLevel MCP Server

AI agents use update-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.

Why update-estimate is rated Medium

This tool modifies an estimate record, which is a write operation. While estimates are business documents that may have financial implications, the action itself is reversible (can be updated again) and does not commit financial transactions or delete data. Severity is medium because incorrect estimates could mislead clients or internal processes, but the operation remains editable and undoable.

From the tool's definition Tool name 'update-estimate' and description 'Update an existing estimate with new details' indicate modification of existing data in a reversible manner.

Questions about update-estimate

What does the update-estimate tool do? +

Update an existing estimate with new details. 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.

How do I enforce a policy on update-estimate? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for update-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.

What risk level is update-estimate? +

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

Can I rate-limit update-estimate? +

Yes. Add a rate_limit block to the update-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.

How do I block update-estimate completely? +

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

What MCP server provides update-estimate? +

update-estimate is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// 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 GoHighLevel MCP Server'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.