This record as markdown: /tools/aiwerk-mcp-server-ghl/phone-system-purchase-phone-number.md
What phone_system_purchase_phone_number does on Ghl
AI agents call phone_system_purchase_phone_number 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 |
|---|---|---|---|
region | string | null | — | Region where the number is being purchased |
locality | string | null | — | Locality where the number is being purchased |
bundleSid | string | null | — | Twilio bundle SID for regulatory compliance |
addressSid | string | null | — | Twilio address SID for compliance |
locationId | string | — | The unique identifier of the location Defaults to GHL_LOCATION_ID when omitted. |
numberType | string | — | Type of phone number |
countryCode | string | — | ISO 3166-1 alpha-2 country code of the number |
phoneNumber | string | Yes | The phone number to purchase |
fingerprintId | string | null | — | Unique request ID for idempotency (fingerprint of the purchase request) |
skipLocationKYC | boolean | null | — | Skip location-level KYC verification if agency-level compliance has already been verified |
Parameters from the server's own tool schema.
Why phone_system_purchase_phone_number is rated Low
Even though phone_system_purchase_phone_number 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
The rule that runs phone_system_purchase_phone_number 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_purchase_phone_number, this is the rule to start with:
phone_system_purchase_phone_number 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_purchase_phone_number call is checked against it from then on.
Questions about phone_system_purchase_phone_number
Purchase a phone number. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
phone_system_purchase_phone_number accepts 10 parameters: region, locality, bundleSid, addressSid, locationId, numberType, countryCode, phoneNumber, fingerprintId, skipLocationKYC. Required: phoneNumber. 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_purchase_phone_number: 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_purchase_phone_number 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_purchase_phone_number 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_purchase_phone_number. 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_purchase_phone_number 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