meta.custom_audiences.create_saved · Ads MCP: Risk & Policy

WHAT IT DOES

What meta.custom_audiences.create_saved does on Ads

AI agents use meta.custom_audiences.create_saved to create or update resources in Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ads environment.

WHY IT NEEDS A POLICY

Why meta.custom_audiences.create_saved needs a policy

This tool creates (writes) new custom audience configurations in Meta's advertising platform. While reversible and not destructive, it has significant business impact as custom audiences are core to ad targeting and campaign effectiveness. High severity reflects that an AI agent misconfiguring audiences could disrupt ad campaigns or create unintended targeting rules affecting ad spend and reach.

From the tool's definition Tool name 'create_saved' and description explicitly state it creates a Meta custom audience. The operation is reversible (audiences can be deleted) and creates new data structures in the Meta Ads system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

meta.custom_audiences.create_saved Rate-limited

meta.custom_audiences.create_saved stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta.custom_audiences.create_saved": {
      "limits": [
        {
          "counter": "meta.custom_audiences.create_saved_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ads, so you can run agents against it safely.

FAQ

Questions about meta.custom_audiences.create_saved

What does the meta.custom_audiences.create_saved tool do? +

Create a saved Meta custom audience from a rule (pixel events, app events, page engagement, or video views). The rule object passes through verbatim; consult Meta. It is categorised as a Write tool in the Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on meta.custom_audiences.create_saved? +

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

What risk level is meta.custom_audiences.create_saved? +

meta.custom_audiences.create_saved is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit meta.custom_audiences.create_saved? +

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

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

meta.custom_audiences.create_saved 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.