create_marketing_audience
Create an owner-private reusable audience definition.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-marketing-audience.md
What create_marketing_audience does on Meta Council
AI agents use create_marketing_audience to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
channels | array | — | |
description | string | — | |
pain_points | string | — |
Parameters from the server's own tool schema.
Why create_marketing_audience is rated Medium
This tool creates and stores new marketing audience data, which is a reversible write operation. While it adds data to the system, it can be deleted or modified later if needed. It is not a destructive deletion, financial transaction, or arbitrary code execution.
From the tool's definition create_marketing_audience performs a create action that generates a new 'reusable audience definition' which is data that persists in the marketing system. The tool modifies the marketing database by adding a new audience record.
Attacks that exploit this kind of access
The rule that runs create_marketing_audience safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_marketing_audience, this is the rule to start with:
create_marketing_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every create_marketing_audience call is checked against it from then on.
Questions about create_marketing_audience
Create an owner-private reusable audience definition. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_marketing_audience accepts 4 parameters: name, channels, description, pain_points. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for create_marketing_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 Council. Nothing to install.
create_marketing_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_marketing_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_marketing_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_marketing_audience is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue