Low Risk

estimate_audience_size

estimate_audience_size

How to control estimate_audience_size ↓

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

Low Risk

An audience size estimation tool queries campaign or targeting data to return metrics, producing no side effects on the advertising account, campaign structure, or financial commitments. The empty description lowers confidence slightly, but the tool name and server context strongly indicate read-only analytics. Confidence is reduced from 0.90 to 0.85 due to the missing description.

From the tool's definition Tool name 'estimate_audience_size' and the server's stated purpose to 'retrieve performance data' and 'analyze Meta advertising campaigns' indicate a data retrieval operation.

Documented attack patterns abuse exactly the kind of access estimate_audience_size 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 estimate_audience_size:

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

estimate_audience_size 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 Ads MCP — 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.

Go deeper

What does the estimate_audience_size tool do? +

estimate_audience_size. It is categorised as a Read tool in the Meta Ads MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on estimate_audience_size? +

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

What risk level is estimate_audience_size? +

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

Can I rate-limit estimate_audience_size? +

Yes. Add a rate_limit block to the estimate_audience_size 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 estimate_audience_size completely? +

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

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

Enforce policy on every Meta Ads MCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.