set_meta_ad_status
Activate or pause a Meta campaign, ad set, or ad. ACTIVATION STARTS REAL AD SPEND and always requires the human (live chat or an approved card) — agents cannot activate. Pausing stops spend. Use after the user has reviewed a draft and explicitly says to launch, or asks to stop a running ad. [outb...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/set-meta-ad-status.md
What set_meta_ad_status does on Freedom Mcp
AI agents use set_meta_ad_status 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 |
|---|---|---|---|
status | string | Yes | 'ACTIVE' (starts spend — human only) or 'PAUSED' (stops spend) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
object_id | string | Yes | Numeric campaign / ad set / ad id |
Parameters from the server's own tool schema.
Why set_meta_ad_status is rated Critical
Activating ads triggers real financial spend on Meta advertising platforms.
From the tool's definition ACTIVATION STARTS REAL AD SPEND
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_meta_ad_status 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 set_meta_ad_status, this is the rule to start with:
Any call to set_meta_ad_status 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 set_meta_ad_status call is checked against it from then on.
Questions about set_meta_ad_status
Activate or pause a Meta campaign, ad set, or ad. ACTIVATION STARTS REAL AD SPEND and always requires the human (live chat or an approved card) — agents cannot activate. Pausing stops spend. Use after the user has reviewed a draft and explicitly says to launch, or asks to stop a running ad. [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.
set_meta_ad_status accepts 3 parameters: status, companyId, object_id. Required: status, companyId, object_id. 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 set_meta_ad_status: 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.
set_meta_ad_status 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 set_meta_ad_status 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 set_meta_ad_status. 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.
set_meta_ad_status 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