ghl_move_pipeline_stage · GHL MCP Server MCP: Risk & Policy

WHAT IT DOES

What ghl_move_pipeline_stage does on GHL MCP Server

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

WHY IT NEEDS A POLICY

Why ghl_move_pipeline_stage needs a policy

This tool updates an existing opportunity's pipeline stage, which is a data modification. It is not destructive (the record and its data remain intact), not financial (no payment or money movement), and not execute-level (no arbitrary code or external command execution). The severity is medium because incorrect moves could disrupt sales workflows or reporting, but the change is easily reversible.

From the tool's definition Tool description states 'Move a GHL opportunity to a different pipeline stage' — this modifies the state of an opportunity record by changing its stageId. The operation is reversible (a subsequent call can move it back to a prior stage).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ghl_move_pipeline_stage Rate-limited

ghl_move_pipeline_stage 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": {
    "ghl_move_pipeline_stage": {
      "limits": [
        {
          "counter": "ghl_move_pipeline_stage_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about ghl_move_pipeline_stage

What does the ghl_move_pipeline_stage tool do? +

Move a GHL opportunity to a different pipeline stage. Args: - opportunityId (string, required): The opportunity ID (from ghl_get_opportunities) - stageId (string, required): Target stage ID (from ghl_list_pipelines) - status (string, optional): Opportunity status —. It is categorised as a Write tool in the GHL 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 ghl_move_pipeline_stage? +

Register the GHL MCP Server MCP server in PolicyLayer and add a rule for ghl_move_pipeline_stage: 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 MCP Server. Nothing to install.

What risk level is ghl_move_pipeline_stage? +

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

Can I rate-limit ghl_move_pipeline_stage? +

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

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

ghl_move_pipeline_stage is provided by the GHL MCP Server MCP server (mnewby20305/nppw-ghl-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.