locations_put_location

Put Sub-Account (Formerly Location) (requires an agency-level token, not a location PIT)

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/locations-put-location.md

WHAT IT DOES

What locations_put_location does on Ghl

AI agents use locations_put_location to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`city`	string	—	The city where the business is located for which sub-account is created
`name`	string	—	The name for the sub-account/location
`phone`	string	—	The phone number of the business for which sub-account is created
`state`	string	—	The state in which the business operates for which sub-account is created
`social`	object	—	The social media links for location
`twilio`	object	—	The twilio credentials for location
`address`	string	—	The address of the business for which sub-account is created
`country`	string	—	The country in which the business is present for which sub-account is created
`mailgun`	object	—	The mailgun credentials for location
`website`	string	—	The website of the business for which sub-account is created
`settings`	object	—	The default settings for location
`snapshot`	object	—	The snapshot to be updated in the location.

Parameters from the server's own tool schema.

RISK

Why locations_put_location is rated Medium

An AI agent can call locations_put_location faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (mailgun.apiKey) · High parameter count (41 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs locations_put_location 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 locations_put_location, this is the rule to start with:

locations_put_location Rate-limited

locations_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "locations_put_location": {
      "limits": [
        {
          "counter": "locations_put_location_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every locations_put_location call is checked against it from then on.

FAQ

Questions about locations_put_location

What does the locations_put_location tool do? +

Put Sub-Account (Formerly Location) (requires an agency-level token, not a location PIT). It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does locations_put_location accept? +

locations_put_location accepts 12 parameters: city, name, phone, state, social, twilio, address, country, mailgun, website, settings, snapshot. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on locations_put_location? +

Register the Ghl MCP server in PolicyLayer and add a rule for locations_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 Ghl. Nothing to install.

What risk level is locations_put_location? +

locations_put_location is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit locations_put_location? +

Yes. Add a rate_limit block to the locations_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.

How do I block locations_put_location completely? +

Set action: deny in the PolicyLayer policy for locations_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.

What MCP server provides locations_put_location? +

locations_put_location 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.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →