This record as markdown: /tools/aiwerk-mcp-server-ghl/ad-manager-fb-create-page-lead-form.md
What ad_manager_fb_create_page_lead_form does on Ghl
AI agents use ad_manager_fb_create_page_lead_form 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 |
|---|---|---|---|
name | string | Yes | Lead form name |
type | string | Yes | Lead form type |
pageId | string | Yes | Facebook page identifier |
questions | array | Yes | List of questions displayed on the lead form |
locationId | string | — | Location identifier Defaults to GHL_LOCATION_ID when omitted. |
greetingCard | object | — | Greeting card config |
thankYouPage | object | Yes | Thank you page config |
customDisclaimer | object | — | Custom disclaimer config |
privacyPolicyLink | string | Yes | Privacy policy URL |
privacyPolicyText | string | — | Privacy policy text |
questionPageHeadline | string | — | Question page headline |
Parameters from the server's own tool schema.
Why ad_manager_fb_create_page_lead_form is rated Medium
An AI agent can call ad_manager_fb_create_page_lead_form 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 raw HTML/template content (greetingCard.content) · High parameter count (24 properties)
Attacks that exploit this kind of access
The rule that runs ad_manager_fb_create_page_lead_form 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 ad_manager_fb_create_page_lead_form, this is the rule to start with:
ad_manager_fb_create_page_lead_form 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every ad_manager_fb_create_page_lead_form call is checked against it from then on.
Questions about ad_manager_fb_create_page_lead_form
Create page lead form. 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.
ad_manager_fb_create_page_lead_form accepts 11 parameters: name, type, pageId, questions, locationId, greetingCard, thankYouPage, customDisclaimer, privacyPolicyLink, privacyPolicyText, questionPageHeadline. Required: name, type, pageId, questions, thankYouPage, privacyPolicyLink. 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 ad_manager_fb_create_page_lead_form: 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.
ad_manager_fb_create_page_lead_form is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ad_manager_fb_create_page_lead_form 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 ad_manager_fb_create_page_lead_form. 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.
ad_manager_fb_create_page_lead_form 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