Resume/activate a paused campaign
AI agents use resume_campaign to create or update resources in Meta Marketing API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Marketing API MCP Server environment.
This tool changes the status of a campaign from paused to active, which is a reversible state change (it can be paused again). It modifies data but does not delete anything or directly move money. However, activating a campaign will cause it to start spending ad budget, which has indirect financial implications, though the tool itself is a status update operation rather than a direct financial transaction.
From the tool's definition Resume/activate a paused campaign
Attacks that exploit this kind of access
Resume/activate a paused campaign. It is categorised as a Write tool in the Meta Marketing API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for resume_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 Marketing API MCP Server. Nothing to install.
resume_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 resume_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 resume_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.
resume_campaign is provided by the Meta Marketing API MCP Server MCP server (pythonando/meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →