This record as markdown: /tools/aiwerk-mcp-server-ghl/funnels-get-pages-by-funnel-id.md
What funnels_get_pages_by_funnel_id does on Ghl
AI agents call funnels_get_pages_by_funnel_id 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 |
|---|---|---|---|
name | string | — | |
limit | number | Yes | |
offset | number | Yes | |
funnelId | string | Yes | |
locationId | string | — | Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why funnels_get_pages_by_funnel_id is rated Low
Even though funnels_get_pages_by_funnel_id 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 funnels_get_pages_by_funnel_id 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 funnels_get_pages_by_funnel_id, this is the rule to start with:
funnels_get_pages_by_funnel_id 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 funnels_get_pages_by_funnel_id call is checked against it from then on.
Questions about funnels_get_pages_by_funnel_id
Fetch list of funnel pages. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
funnels_get_pages_by_funnel_id accepts 5 parameters: name, limit, offset, funnelId, locationId. Required: limit, offset, funnelId. 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 funnels_get_pages_by_funnel_id: 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.
funnels_get_pages_by_funnel_id 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 funnels_get_pages_by_funnel_id 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 funnels_get_pages_by_funnel_id. 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.
funnels_get_pages_by_funnel_id 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