Medium Risk

update_custom_menu

Update an existing custom menu link for a given company.

How to control update_custom_menu ↓

AI agents use update_custom_menu to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

Medium Risk

This tool modifies existing configuration data (custom menu links) for a company within the GoHighLevel CRM platform. It is reversible—menu links can be updated again or reverted. The blast radius is limited to UI/navigation changes for a specific company's interface, with no financial impact, code execution, or data deletion.

From the tool's definition Tool name 'update_custom_menu' and description 'Update an existing custom menu link for a given company' indicate modification of existing data (custom menu links).

Documented attack patterns abuse exactly the kind of access update_custom_menu 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 update_custom_menu:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_custom_menu": {
      "limits": [
        {
          "counter": "update_custom_menu_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_custom_menu stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the update_custom_menu tool do? +

Update an existing custom menu link for a given company. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_custom_menu? +

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

update_custom_menu is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_custom_menu? +

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

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

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