update_opportunity_status

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

SERVERGhl SOURCEghl-mcp-server

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ghl/update-opportunity-status.md

WHAT IT DOES

What update_opportunity_status does on Ghl

AI agents use update_opportunity_status to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`status`	string	Yes	New status for the opportunity
`opportunityId`	string	Yes	The unique ID of the opportunity

Parameters from the server's own tool schema.

RISK

Why update_opportunity_status is rated Medium

This tool creates or modifies data reversibly (Write category) rather than executing arbitrary code or destroying data. While the severity is high because updating opportunity status can have significant business impact (affecting sales pipeline, forecasting, and business decisions), the operation itself is reversible—a user or system can change the status again.

From the tool's definition The tool 'update_opportunity_status' modifies the status field of an opportunity record with options like 'won' or 'lost'. The description explicitly states it performs an update operation, which is a reversible modification to existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_opportunity_status Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_opportunity_status": {
      "limits": [
        {
          "counter": "update_opportunity_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

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 Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_opportunity_status accept? +

update_opportunity_status accepts 2 parameters: status, opportunityId. Required: status, opportunityId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_opportunity_status? +

Register the Ghl 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 Ghl. 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 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →