Update a Sub-Account (Formerly Location) based on the data provided
AI agents use put-location 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 a sub-account's configuration/properties in GoHighLevel, which is a reversible write operation. The severity is high because incorrect updates to a sub-account (location) could affect business operations, user access, or data configuration across an entire business unit, potentially impacting multiple users or workflows.
From the tool's definition Tool name 'put-location' uses PUT HTTP verb, and description states 'Update a Sub-Account (Formerly Location) based on the data provided' — indicating modification of existing data.
Documented attack patterns abuse exactly the kind of access put-location 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 put-location:
{
"version": "1",
"default": "deny",
"tools": {
"put-location": {
"limits": [
{
"counter": "put-location_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}put-location stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update a Sub-Account (Formerly Location) based on the data provided. 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 put-location: 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.
put-location 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 put-location 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 put-location. 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.
put-location 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.