Lists lead generation forms for a Facebook Page. Lead forms are used with OUTCOME_LEADS campaigns to collect user information. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID - limit (number): Max results (1–100, default 20) Returns f...
AI agents call meta_list_leadgen_forms to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves metadata about existing lead generation forms associated with a Facebook Page. It queries data without side effects—no creation, modification, deletion, or execution of operations. The data returned (form IDs, names, status, creation times) is informational only. Misuse by an AI agent would be limited to unauthorized viewing of form inventory, a low-severity read-only action.
From the tool's definition Tool name contains 'list' and description states 'Lists lead generation forms'; returns 'form IDs, names, status, and creation times' with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access meta_list_leadgen_forms gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_list_leadgen_forms:
{
"version": "1",
"default": "deny",
"tools": {
"meta_list_leadgen_forms": {}
}
}meta_list_leadgen_forms 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.
Lists lead generation forms for a Facebook Page. Lead forms are used with OUTCOME_LEADS campaigns to collect user information. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID - limit (number): Max results (1–100, default 20) Returns form IDs, names, status, and creation times. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_list_leadgen_forms: 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 Meta MCP Server. Nothing to install.
meta_list_leadgen_forms 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 meta_list_leadgen_forms 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 meta_list_leadgen_forms. 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.
meta_list_leadgen_forms is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.