update_marketing_campaign
Update one owned marketing campaign. Campaign status never publishes content.
This record as markdown: /tools/com-meta-council-decision-intelligence/update-marketing-campaign.md
What update_marketing_campaign does on Meta Council
AI agents use update_marketing_campaign 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 | — | |
status | string | — | |
ends_on | string | — | |
brand_id | string | — | Full UUID from the matching list tool. |
channels | array | — | |
objective | string | — | |
starts_on | string | — | |
audience_id | string | — | Full UUID from the matching list tool. |
campaign_id | string | Yes | Full UUID from the matching list tool. |
Parameters from the server's own tool schema.
Why update_marketing_campaign is rated Medium
This tool creates or modifies campaign data (status, settings, targeting, etc.) in a reversible manner. The update operation is Write-category because changes can be undone or corrected, and no content is automatically published.
From the tool's definition Tool description explicitly states 'Update one owned marketing campaign', using the verb 'Update' which modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs update_marketing_campaign 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_campaign, this is the rule to start with:
update_marketing_campaign 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_campaign call is checked against it from then on.
Questions about update_marketing_campaign
Update one owned marketing campaign. Campaign status never publishes content. 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_campaign accepts 9 parameters: name, status, ends_on, brand_id, channels, objective, starts_on, audience_id, campaign_id. Required: campaign_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_campaign: 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_campaign 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_campaign 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_campaign. 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_campaign 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