Lists Custom Audiences in a Meta Ads account. Returns id,
AI agents call meta_ads_audiences_list to retrieve information from Mureo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates audience data from Meta Ads without modifying, deleting, or executing external operations. It is a read-only query. Severity is medium rather than low because: (1) audience lists may contain sensitive information about customer segmentation, targeting criteria, or business strategy; (2) unauthorized enumeration could inform competitive intelligence or social engineering; (3) the…
From the tool's definition Tool name 'meta_ads_audiences_list' and description 'Lists Custom Audiences in a Meta Ads account' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access meta_ads_audiences_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_ads_audiences_list:
{
"version": "1",
"default": "deny",
"tools": {
"meta_ads_audiences_list": {}
}
}meta_ads_audiences_list 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 Custom Audiences in a Meta Ads account. Returns id,. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_audiences_list: 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.
meta_ads_audiences_list 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_ads_audiences_list 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_ads_audiences_list. 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_ads_audiences_list 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.
Start from Mureo, 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.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.