Get campaigns for a Meta Ads account with optional filtering. Note: By default, the Meta API returns a subset of available fields. Other fields like 'effective_status', 'spend_cap', 'budget_remaining', 'promoted_object', 'source_campaign_id', etc., might be available but require specifying them i...
AI agents call get_campaigns to retrieve information from Meta Ads MCP 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 campaign data without any side effects or modifications. It is a read-only operation that fetches existing advertising campaign information from a Meta Ads account. While access to advertising account data could have business value, the read-only nature and lack of irreversible actions places it firmly in the Read category with low severity.
From the tool's definition Tool name is 'get_campaigns' and description states 'Get campaigns for a Meta Ads account with optional filtering.' The parameters include account_id, access_token, and limit, with no mention of modifying, creating, or deleting data.
Documented attack patterns abuse exactly the kind of access get_campaigns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_campaigns:
{
"version": "1",
"default": "deny",
"tools": {
"get_campaigns": {}
}
}get_campaigns 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.
Get campaigns for a Meta Ads account with optional filtering. Note: By default, the Meta API returns a subset of available fields. Other fields like 'effective_status', 'spend_cap', 'budget_remaining', 'promoted_object', 'source_campaign_id', etc., might be available but require specifying them in the API call (currently not exposed by this tool's parameters). Args: account_id: Meta Ads account ID (format: act_XXXXXXXXX) access_token: Meta API access token (optional - will use cached token if not provided) limit: Maximum number of campaigns to return (default: 10) status_filter: Filter by effective status (e.g., 'ACTIVE', 'PAUSED', 'ARCHIVED'). Maps to the 'effective_status' API parameter, which expects an array (this function handles the required JSON formatting). Leave empty for all statuses. objective_filter: Filter by campaign objective(s). Can be a single objective string or a list of objectives. Valid objectives: 'OUTCOME_AWARENESS', 'OUTCOME_TRAFFIC', 'OUTCOME_ENGAGEMENT', 'OUTCOME_LEADS', 'OUTCOME_SALES', 'OUTCOME_APP_PROMOTION'. Examples: 'OUTCOME_LEADS' or ['OUTCOME_LEADS', 'OUTCOME_SALES']. Leave empty for all objectives. after: Pagination cursor to get the next set of results. It is categorised as a Read tool in the Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the Meta Ads MCP server in PolicyLayer and add a rule for get_campaigns: 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 Ads MCP. Nothing to install.
get_campaigns 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 get_campaigns 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 get_campaigns. 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.
get_campaigns is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.