Critical Risk →

delete_caller_id

Delete a caller ID

How to control delete_caller_id ↓

AI agents call delete_caller_id 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.

Critical Risk

This tool permanently removes a caller ID configuration, which cannot be undone. Deletion of communication identifiers is a destructive operation that could disrupt business communications if misused by an AI agent (e.g., deleting active caller IDs needed for customer outreach).

From the tool's definition Tool name is 'delete_caller_id' and description states 'Delete a caller ID'. The word 'Delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_caller_id gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_caller_id:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_caller_id"
  ]
}

delete_caller_id disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_caller_id tool do? +

Delete a caller ID. 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 delete_caller_id? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for delete_caller_id: 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 delete_caller_id? +

delete_caller_id 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 delete_caller_id? +

Yes. Add a rate_limit block to the delete_caller_id 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 delete_caller_id completely? +

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

delete_caller_id 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.

Enforce policy on every GoHighLevel MCP Server tool call.

Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.