Gets performance insights for campaigns in a Meta ad account. Args: - ad_account_id (string): Ad account ID - campaign_id (string, optional): Specific campaign ID (omit for all campaigns) - date_preset (string): Date range preset (default: last_30d) - since (string, optional): Custom start date Y...
AI agents call meta_get_campaign_insights 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 reports analytics data from Meta ad accounts without modifying any state, executing code, or performing financial transactions. It is a pure read operation analogous to a SELECT query. Confidence is high because the description explicitly uses 'gets' and 'returns' language indicating data retrieval only.
From the tool's definition Tool description states it 'Gets performance insights for campaigns' and 'Returns per-campaign spend, impressions, clicks, CTR, and actions.' All arguments are filters/parameters for querying data (ad_account_id, campaign_id, date_preset, breakdowns).
Documented attack patterns abuse exactly the kind of access meta_get_campaign_insights 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_get_campaign_insights:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_campaign_insights": {}
}
}meta_get_campaign_insights 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.
Gets performance insights for campaigns in a Meta ad account. Args: - ad_account_id (string): Ad account ID - campaign_id (string, optional): Specific campaign ID (omit for all campaigns) - date_preset (string): Date range preset (default: last_30d) - since (string, optional): Custom start date YYYY-MM-DD - until (string, optional): Custom end date YYYY-MM-DD - breakdowns (string[], optional): Segment by age, gender, country, device_platform, etc. Returns per-campaign spend, impressions, clicks, CTR, and actions. 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_get_campaign_insights: 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_get_campaign_insights 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_get_campaign_insights 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_get_campaign_insights. 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_get_campaign_insights 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.