This record as markdown: /tools/aiwerk-mcp-server-ghl/users-search-users.md
What users_search_users does on Ghl
AI agents call users_search_users 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 |
|---|---|---|---|
ids | string | — | List of User IDs to be filtered in the search |
role | string | — | Role of the users to be filtered in the search |
skip | string | — | No of results to be skipped before returning the result |
sort | string | — | The field on which sort is applied in which the results need to be sorted. Default is based on the first and last name |
type | string | — | Type of the users to be filtered in the search |
limit | string | — | No of results to be limited before returning the result |
query | string | — | The search term for the user is matched based on the user full name, email or phone |
companyId | string | Yes | Company ID in which the search needs to be performed |
locationId | string | — | Location ID in which the search needs to be performed Defaults to GHL_LOCATION_ID when omitted. |
sortDirection | string | — | The direction in which the results need to be sorted |
enabled2waySync | boolean | — |
Parameters from the server's own tool schema.
Why users_search_users is rated Low
Even though users_search_users 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 (11 properties)
Attacks that exploit this kind of access
The rule that runs users_search_users 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 users_search_users, this is the rule to start with:
users_search_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every users_search_users call is checked against it from then on.
Questions about users_search_users
Search Users. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
users_search_users accepts 11 parameters: ids, role, skip, sort, type, limit, query, companyId, locationId, sortDirection, enabled2waySync. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for users_search_users: 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.
users_search_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the users_search_users 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 users_search_users. 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.
users_search_users 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue