Update a Meta campaign
AI agents use wafle_ads_campaign_update_budget to create or update resources in wafle MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your wafle MCP server environment.
This tool creates or modifies data reversibly by updating campaign budgets on Meta's advertising platform. While it affects spending and business operations (increasing blast radius to 'high' severity), it is not a Financial transaction itself—no money is moved, only budget allocation is adjusted. It is reversible (budgets can be adjusted back), so it does not qualify as Destructive.
From the tool's definition Tool name contains 'update' and description states 'Update a Meta campaign'; the operation modifies campaign budget settings which are reversible changes to advertising configuration.
Attacks that exploit this kind of access
Update a Meta campaign. It is categorised as a Write tool in the wafle MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_ads_campaign_update_budget: 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 wafle MCP server. Nothing to install.
wafle_ads_campaign_update_budget 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 wafle_ads_campaign_update_budget 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 wafle_ads_campaign_update_budget. 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.
wafle_ads_campaign_update_budget is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →