Pause Sub account for given locationId
AI agents invoke pause-location-deprecated to trigger actions in GoHighLevel MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Pausing a sub-account is an operational action that affects the entire account's functionality (disabling services, workflows, communications, etc.) for that location. It's not a simple data read or write — it triggers a state change on an external system.
From the tool's definition 'Pause Sub account for given locationId' — pauses an account, which is an external operational state change
Documented attack patterns abuse exactly the kind of access pause-location-deprecated gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pause-location-deprecated:
{
"version": "1",
"default": "deny",
"tools": {
"pause-location-deprecated": {
"limits": [
{
"counter": "pause-location-deprecated_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} pause-location-deprecated stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Pause Sub account for given locationId. It is categorised as a Execute tool in the GoHighLevel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for pause-location-deprecated: 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.
pause-location-deprecated is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pause-location-deprecated 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 pause-location-deprecated. 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.
pause-location-deprecated 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.
Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.