Resumes a paused campaign by setting its status to ACTIVE.
AI agents use meta_ads_campaigns_enable to create or update resources in Mureo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mureo environment.
This tool modifies the status of an existing Meta Ads campaign from PAUSED to ACTIVE. It is a reversible state change (the campaign can be paused again), so it falls under Write rather than Execute or Destructive. However, enabling a campaign can trigger ad spend, giving it medium severity — a misused activation could cause unintended budget consumption, though it doesn't directly move money itself.
From the tool's definition Resumes a paused campaign by setting its status to ACTIVE
Documented attack patterns abuse exactly the kind of access meta_ads_campaigns_enable gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_ads_campaigns_enable:
{
"version": "1",
"default": "deny",
"tools": {
"meta_ads_campaigns_enable": {
"limits": [
{
"counter": "meta_ads_campaigns_enable_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meta_ads_campaigns_enable 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.
Resumes a paused campaign by setting its status to ACTIVE. It is categorised as a Write tool in the Mureo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_campaigns_enable: 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 Mureo. Nothing to install.
meta_ads_campaigns_enable 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 meta_ads_campaigns_enable 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 meta_ads_campaigns_enable. 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.
meta_ads_campaigns_enable is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.