meta_ads_ads_list
Lists ads in a Meta Ads account, optionally scoped to one ad
This record as markdown: /tools/logly-mureo/meta-ads-ads-list.md
What meta_ads_ads_list does on Mureo
AI agents call meta_ads_ads_list 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.
Why meta_ads_ads_list is rated Low
This is a straightforward read operation that queries and returns ad information from Meta Ads. There is no data creation, modification, deletion, code execution, or financial transaction involved. The severity is low because listing ads poses minimal risk even if misused by an AI agent — it only exposes advertising account contents without the ability to alter campaigns, spend money, or trigger external operations.
From the tool's definition Tool name includes 'list' and description states 'Lists ads in a Meta Ads account, optionally scoped to one ad' — purely retrieves/queries data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs meta_ads_ads_list 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_ads_list, this is the rule to start with:
meta_ads_ads_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every meta_ads_ads_list call is checked against it from then on.
Questions about meta_ads_ads_list
Lists ads in a Meta Ads account, optionally scoped to one ad. 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_ads_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_ads_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_ads_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_ads_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_ads_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.
More on Mureo, and thousands of servers like it.
This server
Across the catalogue