Create a custom audience
AI agents use create_custom_audience to create or update resources in Meta Marketing API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Marketing API MCP Server environment.
This tool creates new data (custom audience segments) within Meta's advertising platform, which is reversible (audiences can be deleted or modified). It is not destructive (audiences persist and can be undone), not a read operation, and not financial.
From the tool's definition Tool is named 'create_custom_audience' and described as 'Create a custom audience'. The verb 'create' indicates data creation. The context of Meta Marketing API for advertising shows this creates audience segments for ad targeting purposes.
Attacks that exploit this kind of access
Create a custom audience. It is categorised as a Write tool in the Meta Marketing API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for 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 Marketing API MCP Server. Nothing to install.
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 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 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.
create_custom_audience is provided by the Meta Marketing API MCP Server MCP server (pythonando/meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →