List all pipelines in GoHighLevel with their stage names and IDs. Use this to look up stageId values before calling ghl_move_pipeline_stage. Returns: All pipelines, each with pipeline ID, name, and a list of stages (id + name). Example output: Pipeline: Residential (id: abc123) Stage: New Lead (i...
AI agents call ghl_list_pipelines to retrieve information from GHL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing pipeline configuration data from GoHighLevel without modifying or triggering any actions. It is purely informational, serving as a lookup mechanism to support other tools like ghl_move_pipeline_stage. The blast radius of misuse is minimal—an agent could only discover pipeline structures, not alter them or trigger unwanted workflows.
From the tool's definition Tool description states 'List all pipelines' and 'Returns: All pipelines, each with pipeline ID, name, and a list of stages'. The example output shows read-only retrieval of pipeline metadata. No modifications, deletions, or external executions occur.
Attacks that exploit this kind of access
List all pipelines in GoHighLevel with their stage names and IDs. Use this to look up stageId values before calling ghl_move_pipeline_stage. Returns: All pipelines, each with pipeline ID, name, and a list of stages (id + name). Example output: Pipeline: Residential (id: abc123) Stage: New Lead (id: stage_111) Stage: Estimate Sent (id: stage_222) Stage: Booked (id: stage_333). It is categorised as a Read tool in the GHL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GHL MCP Server MCP server in PolicyLayer and add a rule for ghl_list_pipelines: 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.
ghl_list_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ghl_list_pipelines 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 ghl_list_pipelines. 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.
ghl_list_pipelines 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.
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 →