release_phone_number

Release/delete a phone number

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/release-phone-number.md

What release_phone_number does on GoHighLevel MCP Server

AI agents call release_phone_number to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why release_phone_number is rated Critical

Releasing/deleting a phone number is an irreversible operation that cannot be undone. Once deleted, the phone number is no longer available and associated data or configurations tied to it are lost. This qualifies as Destructive rather than Write because the action is permanent. In a CRM context, deleting phone numbers could disrupt communications, customer records, and workflows.

From the tool's definition Tool name 'release_phone_number' and description 'Release/delete a phone number' explicitly indicate irreversible deletion of a phone number resource.

Questions about release_phone_number

What does the release_phone_number tool do? +

Release/delete a phone number. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on release_phone_number? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for release_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 GoHighLevel MCP Server. Nothing to install.

What risk level is release_phone_number? +

release_phone_number is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit release_phone_number? +

Yes. Add a rate_limit block to the release_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.

How do I block release_phone_number completely? +

Set action: deny in the PolicyLayer policy for release_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.

What MCP server provides release_phone_number? +

release_phone_number is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.