meta_ads_leads_get

Retrieves submitted leads for a single form. Returns per

SERVERMureo SOURCElogly/mureo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/meta-ads-leads-get.md

WHAT IT DOES

What meta_ads_leads_get does on Mureo

AI agents call meta_ads_leads_get to retrieve information from Mureo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why meta_ads_leads_get is rated Low

The verb 'Retrieves' and the absence of any side effects, destructive actions, or data modification language classify this as a Read operation. It queries existing lead data without creating, updating, deleting, or executing external operations.

From the tool's definition Tool name 'meta_ads_leads_get' and description 'Retrieves submitted leads for a single form' indicate a read-only retrieval operation with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meta_ads_leads_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meta_ads_leads_get, this is the rule to start with:

meta_ads_leads_get Allowed

meta_ads_leads_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta_ads_leads_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every meta_ads_leads_get call is checked against it from then on.

FAQ

Questions about meta_ads_leads_get

What does the meta_ads_leads_get tool do? +

Retrieves submitted leads for a single form. Returns per. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on meta_ads_leads_get? +

Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_leads_get: 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 Mureo. Nothing to install.

What risk level is meta_ads_leads_get? +

meta_ads_leads_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit meta_ads_leads_get? +

Yes. Add a rate_limit block to the meta_ads_leads_get 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.

How do I block meta_ads_leads_get completely? +

Set action: deny in the PolicyLayer policy for meta_ads_leads_get. 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.

What MCP server provides meta_ads_leads_get? +

meta_ads_leads_get is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →