update_opportunity_status

Update the status of an opportunity (won, lost, etc.)

SERVERGoHighLevel MCP Server SOURCEhridayshah7/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/hridayshah7-gohighlevel-mcp/update-opportunity-status.md

What update_opportunity_status does on GoHighLevel MCP Server

AI agents use update_opportunity_status 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_opportunity_status is rated Medium

The tool modifies opportunity data reversibly by updating status values. This is categorized as Write rather than Execute because it performs a specific data mutation rather than executing arbitrary code or commands.

From the tool's definition Tool description states 'Update the status of an opportunity' which modifies existing opportunity records by changing their status field (won, lost, etc.). This is a write operation that changes data state.

Questions about update_opportunity_status

What does the update_opportunity_status tool do? +

Update the status of an opportunity (won, lost, etc.). 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_opportunity_status? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for update_opportunity_status: 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_opportunity_status? +

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

Can I rate-limit update_opportunity_status? +

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

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

update_opportunity_status is provided by the GoHighLevel MCP Server MCP server (hridayshah7/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.