Create a new estimate
AI agents use create_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 creates new data (an estimate/quote document) which can be modified or deleted later, making it a Write operation rather than Destructive. In a CRM context, creating estimates is a normal business operation but carries medium severity due to potential financial implications if estimates commit pricing or obligations, though the estimate itself is typically preliminary and reversible.
From the tool's definition Tool name 'create_estimate' with description 'Create a new estimate' indicates creation of a new record. This is a reversible write operation creating a business document (estimate) in the CRM system.
Attacks that exploit this kind of access
Create a new estimate. 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 create_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.
create_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 create_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 create_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.
create_estimate is provided by the GoHighLevel MCP Server MCP server (mindflowedstudios/mindflowed_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →