meta_ads_catalogs_list

Lists Meta Commerce Catalogs owned by a Business. Returns

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-catalogs-list.md

WHAT IT DOES

What meta_ads_catalogs_list does on Mureo

AI agents call meta_ads_catalogs_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.

RISK

Why meta_ads_catalogs_list is rated Low

This tool queries and returns data about Meta Commerce Catalogs without modifying, deleting, or executing operations. It fits the 'Read' category. Severity is medium (not low) because it exposes business advertising assets and catalog structure that could inform competitive or targeting analysis if misused by an AI agent without proper oversight, though the data itself is not financial or destructive.

From the tool's definition Tool name 'meta_ads_catalogs_list' and description 'Lists Meta Commerce Catalogs owned by a Business' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meta_ads_catalogs_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_catalogs_list, this is the rule to start with:

meta_ads_catalogs_list Allowed

meta_ads_catalogs_list 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_catalogs_list": {}
  }
}

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_catalogs_list call is checked against it from then on.

FAQ

Questions about meta_ads_catalogs_list

What does the meta_ads_catalogs_list tool do? +

Lists Meta Commerce Catalogs owned by a Business. Returns. 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_catalogs_list? +

Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_catalogs_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.

What risk level is meta_ads_catalogs_list? +

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

Can I rate-limit meta_ads_catalogs_list? +

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

How do I block meta_ads_catalogs_list completely? +

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

What MCP server provides meta_ads_catalogs_list? +

meta_ads_catalogs_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.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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