This record as markdown: /tools/aiwerk-mcp-server-ghl/phone-system-active-numbers.md
What phone_system_active_numbers does on Ghl
AI agents call phone_system_active_numbers 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 |
|---|---|---|---|
page | number | — | The page index for pagination. The default is 0. |
pageSize | number | — | How many resources to return in each list page. The default is 50, and the maximum is 1000. |
locationId | string | — | The unique identifier of the location Defaults to GHL_LOCATION_ID when omitted. |
searchFilter | string | — | Filter numbers by phone number pattern. Supports partial matching (e.g., "+91" to find all Indian numbers). |
skipNumberPool | boolean | — | Whether to exclude numbers that are assigned to number pools. Default is true. |
Parameters from the server's own tool schema.
Why phone_system_active_numbers is rated Low
Even though phone_system_active_numbers 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.
Attacks that exploit this kind of access
The rule that runs phone_system_active_numbers 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 phone_system_active_numbers, this is the rule to start with:
phone_system_active_numbers 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 phone_system_active_numbers call is checked against it from then on.
Questions about phone_system_active_numbers
List active numbers. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
phone_system_active_numbers accepts 5 parameters: page, pageSize, locationId, searchFilter, skipNumberPool. 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 phone_system_active_numbers: 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.
phone_system_active_numbers 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 phone_system_active_numbers 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 phone_system_active_numbers. 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.
phone_system_active_numbers 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