This record as markdown: /tools/aiwerk-mcp-server-ghl/emails-fetch-campaigns.md
What emails_fetch_campaigns does on Ghl
AI agents call emails_fetch_campaigns to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Filter campaigns by name |
limit | number | — | Maximum number of campaigns to return. Defaults to 10, maximum is 100 |
offset | number | — | Number of campaigns to skip for pagination |
status | string | — | Filter by schedule status |
archived | boolean | — | Filter archived campaigns |
parentId | string | — | Filter campaigns by parent folder ID |
showStats | boolean | — | When true, returns campaign statistics including delivered count, opened count, clicked count and revenue if available for the campaign. When false, returns cam |
locationId | string | — | Location ID to fetch campaigns from Defaults to GHL_LOCATION_ID when omitted. |
emailStatus | string | — | Filter by email delivery status |
campaignsOnly | boolean | — | Return only campaigns, excluding folders |
limitedFields | boolean | — | When true, returns only essential campaign fields like id, templateDataDownloadUrl, updatedAt, type, templateType, templateId, downloadUrl and isPlainText. When |
Parameters from the server's own tool schema.
Why emails_fetch_campaigns is rated Low
Even though emails_fetch_campaigns only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs emails_fetch_campaigns 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 emails_fetch_campaigns, this is the rule to start with:
emails_fetch_campaigns is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every emails_fetch_campaigns call is checked against it from then on.
Questions about emails_fetch_campaigns
Get Campaigns. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
emails_fetch_campaigns accepts 11 parameters: name, limit, offset, status, archived, parentId, showStats, locationId, emailStatus, campaignsOnly, limitedFields. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for emails_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 Ghl. Nothing to install.
emails_fetch_campaigns 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 emails_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.
Set action: deny in the PolicyLayer policy for emails_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.
emails_fetch_campaigns is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue