custom_menus_get_custom_menus
Get Custom Menu Links (requires an agency-level token, not a location PIT)
This record as markdown: /tools/aiwerk-mcp-server-ghl/custom-menus-get-custom-menus.md
What custom_menus_get_custom_menus does on Ghl
AI agents call custom_menus_get_custom_menus to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number of items to skip for pagination |
limit | number | — | Maximum number of items to return |
query | string | — | Search query to filter custom menus by name, supports partial || full names |
locationId | string | — | Unique identifier of the location Defaults to GHL_LOCATION_ID when omitted. |
showOnCompany | boolean | — | Filter to show only agency-level menu links. When omitted, fetches both agency and sub-account menu links. Ignored if locationId is provided |
Parameters from the server's own tool schema.
Why custom_menus_get_custom_menus is rated Low
Even though custom_menus_get_custom_menus only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs custom_menus_get_custom_menus 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_get_custom_menus, this is the rule to start with:
custom_menus_get_custom_menus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every custom_menus_get_custom_menus call is checked against it from then on.
Questions about custom_menus_get_custom_menus
Get Custom Menu Links (requires an agency-level token, not a location PIT). It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
custom_menus_get_custom_menus accepts 5 parameters: skip, limit, query, locationId, showOnCompany. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for custom_menus_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 Ghl. Nothing to install.
custom_menus_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 custom_menus_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 custom_menus_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.
custom_menus_get_custom_menus 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.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue