Lists ad sets for a campaign or ad account. Args: - campaign_id (string, optional): Filter by campaign ID - ad_account_id (string, optional): Ad account ID (use if not filtering by campaign) - status_filter (string[], optional): ACTIVE, PAUSED, ARCHIVED, DELETED - limit (number): Max results (def...
AI agents call meta_list_adsets to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing ad set data without modifying, creating, deleting, or executing any operations. It has no side effects on the Meta platform. The blast radius of misuse is minimal—an agent could list ad sets belonging to an account, but cannot modify them or access sensitive user data beyond metadata about ad campaigns already owned by the account holder. This is a standard Read operation.
From the tool's definition Tool name is 'meta_list_adsets' and description states it 'Lists ad sets for a campaign or ad account.' The arguments are all query parameters (campaign_id, ad_account_id, status_filter, limit, after) with no write, delete, or execute capabilities.
Documented attack patterns abuse exactly the kind of access meta_list_adsets gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_list_adsets:
{
"version": "1",
"default": "deny",
"tools": {
"meta_list_adsets": {}
}
}meta_list_adsets 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 ad sets for a campaign or ad account. Args: - campaign_id (string, optional): Filter by campaign ID - ad_account_id (string, optional): Ad account ID (use if not filtering by campaign) - status_filter (string[], optional): ACTIVE, PAUSED, ARCHIVED, DELETED - limit (number): Max results (default 20) - after (string, optional): Pagination cursor Provide either campaign_id or ad_account_id. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_list_adsets: 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 Meta MCP Server. Nothing to install.
meta_list_adsets 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_list_adsets 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_list_adsets. 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_list_adsets is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.