meta_ads_targeting_categories
Lists a full Meta targeting category catalogue for the given
This record as markdown: /tools/logly-mureo/meta-ads-targeting-categories.md
What meta_ads_targeting_categories does on Mureo
AI agents call meta_ads_targeting_categories 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_targeting_categories is rated Low
This tool queries and returns metadata about available targeting categories in Meta Ads. It performs a read-only lookup operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal — an agent listing available categories cannot cause financial loss, delete data, or trigger unwanted ad campaigns.
From the tool's definition Tool name and description indicate 'Lists a full Meta targeting category catalogue' — a retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
The rule that runs meta_ads_targeting_categories 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_targeting_categories, this is the rule to start with:
meta_ads_targeting_categories 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_targeting_categories call is checked against it from then on.
Questions about meta_ads_targeting_categories
Lists a full Meta targeting category catalogue for the given. 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_targeting_categories: 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_targeting_categories 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_targeting_categories 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_targeting_categories. 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_targeting_categories 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