update_opportunity_status · Ghl MCP: Risk & Policy

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.

WHY IT NEEDS A POLICY

Why update_opportunity_status needs a policy

This tool modifies opportunity state in a CRM system, which is a Write operation. The severity is medium because changing opportunity status could affect sales pipelines, revenue forecasting, and business workflows, but the change is reversible and does not involve financial transactions, destructive deletions, or code execution. Confidence is high given the clear description of the update operation.

From the tool's definition Tool name 'update_opportunity_status' and description 'Change the status of a GoHighLevel opportunity' indicate modification of existing opportunity data. The action is reversible (status can be changed again), and no data is permanently deleted or destroyed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ghl, so you can run agents against it safely.

FAQ

Questions about update_opportunity_status

What does the update_opportunity_status tool do? +

Change the status of a GoHighLevel opportunity. 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.

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 (snack-jpg/ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.