fetch-campaigns

Get Campaigns

SERVERGoHighLevel MCP Server SOURCEdrausal/gohighlevel-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/drausal-gohighlevel-mcp/fetch-campaigns.md

WHAT IT DOES

What fetch-campaigns does on GoHighLevel MCP Server

AI agents call fetch-campaigns to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why fetch-campaigns is rated Low

This tool retrieves campaign data from GoHighLevel. It performs a simple query/retrieval operation typical of Read category tools. There is no indication it modifies, deletes, executes code, or creates financial obligations. The blast radius of misuse is limited to unauthorized data access.

From the tool's definition Tool name 'fetch-campaigns' and description 'Get Campaigns' indicate a retrieval operation with no side effects. The verb 'fetch' and 'Get' are standard read operations that query data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch-campaigns safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GoHighLevel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fetch-campaigns, this is the rule to start with:

fetch-campaigns Allowed

fetch-campaigns is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch-campaigns": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GoHighLevel MCP Server, apply this rule, and every fetch-campaigns call is checked against it from then on.

FAQ

Questions about fetch-campaigns

What does the fetch-campaigns tool do? +

Get Campaigns. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch-campaigns? +

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

fetch-campaigns is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch-campaigns? +

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

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

fetch-campaigns is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GoHighLevel MCP Server, and thousands of servers like it.

This server

All 406 GoHighLevel MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →