custom_menus_create_custom_menu

Create Custom Menu Link (requires an agency-level token, not a location PIT)

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 119 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/custom-menus-create-custom-menu.md

WHAT IT DOES

What custom_menus_create_custom_menu does on Ghl

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

Parameter	Type	Required	Description
`url`	string	Yes	URL of the custom menu
`icon`	object	Yes	Icon information for the custom menu
`title`	string	Yes	Title of the custom menu
`openMode`	string	Yes	Mode for opening the menu link
`userRole`	string	Yes	Which user-roles should the menu be accessible to?
`locations`	array	Yes	List of sub-account IDs where the menu should be shown. This list is applicable only when showOnLocation is true and showToAllLocations is false
`allowCamera`	boolean	—	Whether to allow camera access (only for iframe mode)
`showOnCompany`	boolean	Yes	Whether the menu must be displayed on the agency's level
`showOnLocation`	boolean	Yes	Whether the menu must be displayed for sub-accounts level
`allowMicrophone`	boolean	—	Whether to allow microphone access (only for iframe mode)
`showToAllLocations`	boolean	Yes	Whether the menu must be displayed to all sub-accounts

Parameters from the server's own tool schema.

RISK

Why custom_menus_create_custom_menu is rated Medium

An AI agent can call custom_menus_create_custom_menu faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (url) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs custom_menus_create_custom_menu 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 custom_menus_create_custom_menu, this is the rule to start with:

custom_menus_create_custom_menu Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_menus_create_custom_menu": {
      "limits": [
        {
          "counter": "custom_menus_create_custom_menu_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every custom_menus_create_custom_menu call is checked against it from then on.

FAQ

Questions about custom_menus_create_custom_menu

What does the custom_menus_create_custom_menu tool do? +

Create Custom Menu Link (requires an agency-level token, not a location PIT). It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does custom_menus_create_custom_menu accept? +

custom_menus_create_custom_menu accepts 11 parameters: url, icon, title, openMode, userRole, locations, allowCamera, showOnCompany, showOnLocation, allowMicrophone, showToAllLocations. Required: url, icon, title, openMode, userRole, locations, showOnCompany, showOnLocation, showToAllLocations. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on custom_menus_create_custom_menu? +

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

What risk level is custom_menus_create_custom_menu? +

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

Can I rate-limit custom_menus_create_custom_menu? +

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

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

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

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →