Creates a new custom audience in a Meta ad account. Supported types: - CUSTOM: Website visitors (requires Pixel), app activity, or customer list - ENGAGEMENT: People who engaged with your content - VIDEO: People who watched your videos Args: - ad_account_id (string): Ad account ID (e.g., act_1234...
AI agents use meta_create_custom_audience to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool creates and modifies data (custom audiences) within a Meta ad account, which is reversible—audiences can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money. While it could enable targeting for unwanted ads if misused, the primary action is creating a new resource, placing it in the Write category.
From the tool's definition Creates a new custom audience in a Meta ad account. The tool accepts parameters like ad_account_id, name, subtype, and customer_file_source to create audience segments for advertising purposes.
Documented attack patterns abuse exactly the kind of access meta_create_custom_audience 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_create_custom_audience:
{
"version": "1",
"default": "deny",
"tools": {
"meta_create_custom_audience": {
"limits": [
{
"counter": "meta_create_custom_audience_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} meta_create_custom_audience 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.
Free to start. No card required.
Creates a new custom audience in a Meta ad account. Supported types: - CUSTOM: Website visitors (requires Pixel), app activity, or customer list - ENGAGEMENT: People who engaged with your content - VIDEO: People who watched your videos Args: - ad_account_id (string): Ad account ID (e.g., act_123456789) - name (string): Audience name - subtype (string): CUSTOM, ENGAGEMENT, VIDEO, WEBSITE, or APP - description (string, optional): Audience description - customer_file_source (string, optional): For CUSTOM type — USER_PROVIDED_ONLY, PARTNER_PROVIDED_ONLY, BOTH_USER_AND_PARTNER_PROVIDED - retention_days (number, optional): Days to retain audience members (1–180) Returns the new audience ID. Note: Populating the audience with users is a separate step requiring the Audiences API to upload hashed data or configure a rule. It is categorised as a Write tool in the Meta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_create_custom_audience: 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_create_custom_audience is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the meta_create_custom_audience 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_create_custom_audience. 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_create_custom_audience 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.