List ad sets for a campaign
AI agents call list_ad_sets to retrieve information from Meta Marketing API 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 or queries advertising data (ad sets) for a given campaign with no side effects. It fits the Read category as it performs a simple enumeration/listing operation. The severity is low because listing campaign data poses minimal risk even if misused by an AI agent—it discloses information but does not modify, delete, or execute actions that could harm the advertising account.
From the tool's definition Tool name 'list_ad_sets' and description 'List ad sets for a campaign' indicate data retrieval without modification. The verb 'list' is a quintessential read operation that queries and returns existing ad set information.
Attacks that exploit this kind of access
List ad sets for a campaign. It is categorised as a Read tool in the Meta Marketing API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for list_ad_sets: 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 Marketing API MCP Server. Nothing to install.
list_ad_sets 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 list_ad_sets 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 list_ad_sets. 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.
list_ad_sets is provided by the Meta Marketing API MCP Server MCP server (pythonando/meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →