# get-user-by-location

A read tool on the GoHighLevel MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get-user-by-location`. HTML page: https://policylayer.com/tools/drausal-gohighlevel-mcp/get-user-by-location

## Facts

- Tool: `get-user-by-location`
- Server: GoHighLevel MCP Server (`drausal/gohighlevel-mcp`) — https://policylayer.com/tools/drausal-gohighlevel-mcp.md
- Homepage: https://github.com/drausal/gohighlevel-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-user-by-location",
    "arguments": {}
  }
}
```

## Why get-user-by-location is rated Low

This tool performs a simple data retrieval based on location criteria. It has no side effects, does not modify data, execute code, delete information, or involve financial transactions. The blast radius of misuse is minimal—an agent could retrieve user information it shouldn't access, but this is a confidentiality concern rather than a safety/damage concern. Classified as Read with low severity.

From the tool's own definition: "Tool name 'get-user-by-location' and description 'Get User by Location' indicate a retrieval operation. The verb 'Get' is a read-only query operation that retrieves user data filtered by location without modifying any data."

## Use case

AI agents call get-user-by-location to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches GoHighLevel MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-user-by-location": {}
  }
}
```

## Other tools on GoHighLevel MCP Server (405)

- `bulk-delete-media-objects` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/bulk-delete-media-objects.md
- `bulk-delete-social-planner-posts` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/bulk-delete-social-planner-posts.md
- `bulkUpdate` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/bulkupdate.md
- `cancel-invoice-schedule` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/cancel-invoice-schedule.md
- `cancel-scheduled-email-message` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/cancel-scheduled-email-message.md
- `cancel-scheduled-message` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/cancel-scheduled-message.md
- `delete-account` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-account.md
- `delete-action` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-action.md
- `delete-agent` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-agent.md
- `DELETE-an-email-sms-template` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-an-email-sms-template.md
- `delete-appointment-note` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-appointment-note.md
- `delete-association` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-association.md
- `delete-Business` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-business.md
- `delete-calendar` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-calendar.md
- `delete-calendar-resource` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-calendar-resource.md
- `delete-contact` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-contact.md
- `delete-contact-from-workflow` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-contact-from-workflow.md
- `delete-conversation` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-conversation.md
- `delete-coupon` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-coupon.md
- `delete-csv` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-csv.md
- `delete-csv-post` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-csv-post.md
- `delete-custom-field` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-custom-field.md
- `delete-custom-field-2` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-custom-field-2.md
- `delete-custom-field-folder` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-custom-field-folder.md
- `delete-custom-menu` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-custom-menu.md
- `delete-custom-value` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-custom-value.md
- `delete-estimate` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-estimate.md
- `delete-estimate-template` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-estimate-template.md
- `delete-event` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-event.md
- `delete-event-notification` — Destructive — https://policylayer.com/tools/drausal-gohighlevel-mcp/delete-event-notification.md
- …and 375 more: https://policylayer.com/tools/drausal-gohighlevel-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=drausal-gohighlevel-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/drausal-gohighlevel-mcp
