Fetches a collection of custom menus based on specified criteria. This endpoint allows clients to retrieve custom menu configurations, which may include menu items, categories, and associated metadata. The response can be tailored using query parameters for filtering, sorting, and pagination.
AI agents call get-custom-menus to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves menu configuration data without side effects. It uses standard read patterns (filtering, sorting, pagination) typical of data retrieval endpoints. There is no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an AI agent could only access menu configurations it is authorized to view.
From the tool's definition Tool name 'get-custom-menus' and description 'Fetches a collection of custom menus' and 'retrieve custom menu configurations' clearly indicate a read operation. No modification, deletion, or execution of external operations occurs.
Documented attack patterns abuse exactly the kind of access get-custom-menus 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 get-custom-menus:
{
"version": "1",
"default": "deny",
"tools": {
"get-custom-menus": {}
}
}get-custom-menus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetches a collection of custom menus based on specified criteria. This endpoint allows clients to retrieve custom menu configurations, which may include menu items, categories, and associated metadata. The response can be tailored using query parameters for filtering, sorting, and pagination. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get-custom-menus: 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.
get-custom-menus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-custom-menus 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.
Set action: deny in the PolicyLayer policy for get-custom-menus. 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.
get-custom-menus 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.
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.