Low Risk

meta_get_ad_insights

Gets performance insights at the individual ad level. Args: - ad_account_id (string, optional): All ads in account - campaign_id (string, optional): All ads in campaign - adset_id (string, optional): All ads in ad set - ad_id (string, optional): Specific ad - date_preset (string): Date range pres...

How to control meta_get_ad_insights ↓

What meta_get_ad_insights does on Meta MCP Server

AI agents call meta_get_ad_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.

Low Risk

Why meta_get_ad_insights needs a policy

meta_get_ad_insights is a read-only analytics query tool that retrieves existing performance data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—worst case an actor views performance metrics they shouldn't, which is a confidentiality concern but not destructive or financial in nature.

From the tool's definition Tool retrieves performance insights at the individual ad level. Parameters allow filtering by ad_account_id, campaign_id, adset_id, or ad_id, with optional date ranges and breakdown dimensions (age, gender, country, device_platform, etc.).

Documented attack patterns abuse exactly the kind of access meta_get_ad_insights gives an agent:

How to control meta_get_ad_insights

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_ad_insights:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta_get_ad_insights": {}
  }
}

meta_get_ad_insights is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Meta MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about meta_get_ad_insights

What does the meta_get_ad_insights tool do? +

Gets performance insights at the individual ad level. Args: - ad_account_id (string, optional): All ads in account - campaign_id (string, optional): All ads in campaign - adset_id (string, optional): All ads in ad set - ad_id (string, optional): Specific ad - date_preset (string): Date range preset (default: last_30d) - since / until (string, optional): Custom date range YYYY-MM-DD - breakdowns (string[], optional): age, gender, country, device_platform, etc. Provide one of: ad_id, adset_id, 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.

How do I enforce a policy on meta_get_ad_insights? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_get_ad_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.

What risk level is meta_get_ad_insights? +

meta_get_ad_insights is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit meta_get_ad_insights? +

Yes. Add a rate_limit block to the meta_get_ad_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.

How do I block meta_get_ad_insights completely? +

Set action: deny in the PolicyLayer policy for meta_get_ad_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.

What MCP server provides meta_get_ad_insights? +

meta_get_ad_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.

Enforce policy on every Meta MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.