oauth_get_installed_location

Get Location where app is installed (requires an agency-level token, not a location PIT)

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Low RISK CLASS

Category Read

Parameters 102 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/oauth-get-installed-location.md

WHAT IT DOES

What oauth_get_installed_location does on Ghl

AI agents call oauth_get_installed_location 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
`skip`	string	—	Parameter to skip the number installed locations
`appId`	string	Yes	Parameter to search by the appId
`limit`	string	—	Parameter to limit the number installed locations
`query`	string	—	Parameter to search for the installed location by name
`planId`	string	—	Filters out location which are installed for specified app under the specified planId
`onTrial`	boolean	—	Filters out locations which are installed for specified app in trial mode
`companyId`	string	Yes	Parameter to search by the companyId
`versionId`	string	—	VersionId of the app
`locationId`	string	—	locationId Defaults to GHL_LOCATION_ID when omitted.
`isInstalled`	boolean	—	Filters out location which are installed for specified app under the specified company

Parameters from the server's own tool schema.

RISK

Why oauth_get_installed_location is rated Low

Even though oauth_get_installed_location 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

RECOMMENDED RULE

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

oauth_get_installed_location Allowed

oauth_get_installed_location is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oauth_get_installed_location": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about oauth_get_installed_location

What does the oauth_get_installed_location tool do? +

Get Location where app is installed (requires an agency-level token, not a location PIT). It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.

What parameters does oauth_get_installed_location accept? +

oauth_get_installed_location accepts 10 parameters: skip, appId, limit, query, planId, onTrial, companyId, versionId, locationId, isInstalled. Required: appId, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on oauth_get_installed_location? +

Register the Ghl MCP server in PolicyLayer and add a rule for oauth_get_installed_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 oauth_get_installed_location? +

oauth_get_installed_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oauth_get_installed_location? +

Yes. Add a rate_limit block to the oauth_get_installed_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 oauth_get_installed_location completely? +

Set action: deny in the PolicyLayer policy for oauth_get_installed_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 oauth_get_installed_location? +

oauth_get_installed_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →