update_meta_ad_budget
Change the daily budget of a Meta ad set (account currency, major units; structural cap applies). Moves real money, so it always requires the human — agents cannot change budgets. Use when the user explicitly asks to raise or lower spend on a campaign. [outbound-tier — EVERY call needs a manager'...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-meta-ad-budget.md
What update_meta_ad_budget does on Freedom Mcp
AI agents use update_meta_ad_budget to commit financial operations through Freedom Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
adset_id | string | Yes | Numeric ad set id |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
daily_budget | number | Yes | New daily budget, account currency major units |
ad_account_id | string | — | Optional — for currency resolution when several accounts exist |
Parameters from the server's own tool schema.
Why update_meta_ad_budget is rated Critical
Directly modifies advertising spend, committing real financial resources to Meta campaigns.
From the tool's definition Moves real money, change daily budget of a Meta ad set
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs update_meta_ad_budget safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_meta_ad_budget, this is the rule to start with:
Any call to update_meta_ad_budget is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_meta_ad_budget call is checked against it from then on.
Questions about update_meta_ad_budget
Change the daily budget of a Meta ad set (account currency, major units; structural cap applies). Moves real money, so it always requires the human — agents cannot change budgets. Use when the user explicitly asks to raise or lower spend on a campaign. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.]. It is categorised as a Financial tool in the Freedom Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
update_meta_ad_budget accepts 4 parameters: adset_id, companyId, daily_budget, ad_account_id. Required: adset_id, companyId, daily_budget. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for update_meta_ad_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 Freedom Mcp. Nothing to install.
update_meta_ad_budget is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the update_meta_ad_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 update_meta_ad_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.
update_meta_ad_budget is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
Across the catalogue