conversations_user_subscription_change
User Subscription Change
This record as markdown: /tools/aiwerk-mcp-server-ghl/conversations-user-subscription-change.md
What conversations_user_subscription_change does on Ghl
AI agents call conversations_user_subscription_change 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 |
|---|---|---|---|
email | string | Yes | Email address |
contactId | string | Yes | Contact Id |
locationId | string | — | Location Id Defaults to GHL_LOCATION_ID when omitted. |
legal_reason | string | — | Legal reason for the change (required only for resubscribe and resub_all actions) |
legal_description | string | — | Legal description/details |
subscription_action | object | Yes | Subscription action details |
Parameters from the server's own tool schema.
Why conversations_user_subscription_change is rated Low
Even though conversations_user_subscription_change 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 (10 properties)
Attacks that exploit this kind of access
The rule that runs conversations_user_subscription_change 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 conversations_user_subscription_change, this is the rule to start with:
conversations_user_subscription_change 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 conversations_user_subscription_change call is checked against it from then on.
Questions about conversations_user_subscription_change
User Subscription Change. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
conversations_user_subscription_change accepts 6 parameters: email, contactId, locationId, legal_reason, legal_description, subscription_action. Required: email, contactId, subscription_action. 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 conversations_user_subscription_change: 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.
conversations_user_subscription_change 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 conversations_user_subscription_change 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 conversations_user_subscription_change. 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.
conversations_user_subscription_change 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