AI agents call meta.campaigns.list to retrieve information from Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves campaign data for viewing and analysis only. It has no side effects, does not modify or delete data, and does not execute external operations. The blast radius of misuse is minimal — an agent could view campaign performance across accounts but cannot alter budgets, pause campaigns, or modify settings.
From the tool's definition Tool name 'list' and description 'List Meta ad campaigns with status, budgets, and performance metrics' indicate data retrieval with no modification capabilities. Supports 'status filter and pagination' — standard read-only query parameters.
Attacks that exploit this kind of access
List Meta ad campaigns with status, budgets, and performance metrics. Supports status filter and pagination. It is categorised as a Read tool in the Ads MCP Server, which means it retrieves data without modifying state.
Register the Ads MCP server in PolicyLayer and add a rule for meta.campaigns.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 Ads. Nothing to install.
meta.campaigns.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.campaigns.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.campaigns.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.campaigns.list is provided by the Ads MCP server (manlikemuneeb/ads-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 →