list_subscriptions
List subscriptions with optional filtering and pagination
This record as markdown: /tools/ghl/list-subscriptions.md
What list_subscriptions does on Ghl
AI agents call list_subscriptions 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 |
|---|---|---|---|
id | string | — | Subscription ID for filtering |
altId | string | Yes | Alt ID (unique identifier like location ID) |
endAt | string | — | Ending date interval for subscriptions (YYYY-MM-DD) |
limit | number | — | Maximum number of items per page |
offset | number | — | Starting index for pagination |
search | string | — | Search term for subscription name |
altType | string | Yes | Alt Type |
startAt | string | — | Starting date interval for subscriptions (YYYY-MM-DD) |
entityId | string | — | Entity ID for filtering subscriptions |
contactId | string | — | Contact ID for the subscription |
paymentMode | string | — | Mode of payment (live/test) |
entitySourceType | string | — | Source of the subscriptions |
Parameters from the server's own tool schema.
Why list_subscriptions is rated Low
This tool retrieves subscription data without side effects. It queries and returns information using filtering and pagination parameters, which are hallmarks of Read operations. No data is created, modified, deleted, or financial transactions are triggered.
From the tool's definition Tool name is 'list_subscriptions' and description states 'List subscriptions with optional filtering and pagination' — pure retrieval operation with no modification, deletion, or execution of external commands.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs list_subscriptions 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 list_subscriptions, this is the rule to start with:
list_subscriptions 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 list_subscriptions call is checked against it from then on.
Questions about list_subscriptions
List subscriptions with optional filtering and pagination. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
list_subscriptions accepts 12 parameters: id, altId, endAt, limit, offset, search, altType, startAt, entityId, contactId, paymentMode, entitySourceType. Required: altId, altType. 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 list_subscriptions: 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.
list_subscriptions 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 list_subscriptions 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 list_subscriptions. 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.
list_subscriptions is provided by the Ghl MCP server (ghl-mcp-server). 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