AI agents use update_campaign to create or update resources in Meta Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Ads MCP environment.
Update operations are reversible writes that modify campaign configuration (budget, targeting, status, etc.) without deleting data. High severity reflects that misconfigured campaign updates could waste advertising budgets, change targeting in unintended ways, or disrupt active campaigns.
From the tool's definition Tool name is 'update_campaign' with empty description. Sibling tools include create_campaign, create_ad, create_adset, and other campaign/ad management operations, establishing this server's domain as Meta Ads management.
Documented attack patterns abuse exactly the kind of access update_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"update_campaign": {
"limits": [
{
"counter": "update_campaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Free to start. No card required.
update_campaign. It is categorised as a Write tool in the Meta Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta Ads MCP server in PolicyLayer and add a rule for update_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 Ads MCP. Nothing to install.
update_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_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_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_campaign is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.