Gets submitted leads from a lead generation form. Requires: meta_list_pages must be called first to load page tokens. Args: - form_id (string): Lead gen form ID (from meta_list_leadgen_forms) - page_id (string): Page ID (for authentication) - limit (number): Max results (1–100, default 25) - afte...
AI agents call meta_get_leadgen_leads 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 is a retrieval operation (Read category). However, severity is elevated to medium rather than low because lead generation data often contains personally identifiable information (PII) such as names, email addresses, phone numbers, and other contact details.
From the tool's definition Tool name uses 'get' verb and description states 'Gets submitted leads from a lead generation form.' It retrieves data with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access meta_get_leadgen_leads 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_get_leadgen_leads:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_leadgen_leads": {}
}
}meta_get_leadgen_leads 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.
Gets submitted leads from a lead generation form. Requires: meta_list_pages must be called first to load page tokens. Args: - form_id (string): Lead gen form ID (from meta_list_leadgen_forms) - page_id (string): Page ID (for authentication) - limit (number): Max results (1–100, default 25) - after (string, optional): Pagination cursor Returns lead data including field values, creation time, and ad info. 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_get_leadgen_leads: 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_get_leadgen_leads 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_get_leadgen_leads 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_get_leadgen_leads. 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_get_leadgen_leads 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.