Critical Risk →

delete-custom-menu

Removes a specific custom menu from the system. This operation requires authentication and proper permissions. The custom menu is identified by its unique ID, and the operation is performed within the context of a specific company.

How to control delete-custom-menu ↓

What delete-custom-menu does on GoHighLevel MCP Server

AI agents call delete-custom-menu 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

Why delete-custom-menu needs a policy

This tool performs an irreversible deletion operation on custom menu data. Destructive actions are more severe than Write operations because they cannot be undone. An AI agent given this tool could permanently remove important menu structures from a business's system, affecting user experience and workflows across the platform.

From the tool's definition The tool description explicitly states it 'Removes a specific custom menu' - the word 'Removes' indicates irreversible deletion.

Documented attack patterns abuse exactly the kind of access delete-custom-menu gives an agent:

How to control delete-custom-menu

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-custom-menu:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-custom-menu"
  ]
}

delete-custom-menu 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.

Related tools and policies

Go deeper

Questions about delete-custom-menu

What does the delete-custom-menu tool do? +

Removes a specific custom menu from the system. This operation requires authentication and proper permissions. The custom menu is identified by its unique ID, and the operation is performed within the context of a specific company. 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-custom-menu? +

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

delete-custom-menu 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-custom-menu? +

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

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

delete-custom-menu is provided by the GoHighLevel MCP Server MCP server (drausal/gohighlevel-mcp). 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.

Start from GoHighLevel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

406 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.