Switch the active GHL sub-account. All subsequent tool calls will use this account until switched again.
AI agents use switch_subaccount to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.
This tool modifies the active session/context by switching which sub-account is used for all subsequent operations. While it doesn't directly delete or create data, it changes the operational scope in a persistent way that affects all future tool calls.
From the tool's definition Switch the active GHL sub-account. All subsequent tool calls will use this account until switched again.
Attacks that exploit this kind of access
Switch the active GHL sub-account. All subsequent tool calls will use this account until switched again. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for switch_subaccount: 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.
switch_subaccount is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the switch_subaccount 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 switch_subaccount. 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.
switch_subaccount is provided by the GoHighLevel MCP Server MCP server (tailormadeweddings/gohighlevel-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 →