update_marketing_audience
Update fields on one owned audience definition. No delete is exposed over MCP.
This record as markdown: /tools/com-meta-council-decision-intelligence/update-marketing-audience.md
What update_marketing_audience does on Meta Council
AI agents use update_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 | — | |
channels | array | — | |
audience_id | string | Yes | Full UUID from the matching list tool. |
description | string | — | |
pain_points | string | — |
Parameters from the server's own tool schema.
Why update_marketing_audience is rated Medium
This tool modifies existing data (audience definitions) reversibly—updates can be undone or corrected in subsequent calls. It does not delete, execute code, move money, or read-only query. The 'medium' severity reflects the business impact of incorrect audience targeting (potential campaign misallocation or wasted budget), but the reversible nature and lack of destructive capability keep it below 'high'.
From the tool's definition Tool name 'update_marketing_audience' indicates modification of audience data. Description states it can 'update fields on one owned audience definition' and explicitly notes 'no delete is exposed', confirming write capability without destruction.
Attacks that exploit this kind of access
The rule that runs update_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 update_marketing_audience, this is the rule to start with:
update_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 update_marketing_audience call is checked against it from then on.
Questions about update_marketing_audience
Update fields on one owned audience definition. No delete is exposed over MCP. 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.
update_marketing_audience accepts 5 parameters: name, channels, audience_id, description, pain_points. Required: audience_id. 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 update_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.
update_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 update_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 update_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.
update_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