meta.adsets.create · Ads MCP: Risk & Policy

WHAT IT DOES

What meta.adsets.create does on Ads

AI agents use meta.adsets.create to create or update resources in Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ads environment.

WHY IT NEEDS A POLICY

Why meta.adsets.create needs a policy

This tool creates a new ad set in Meta Ads, which is a reversible write operation (ad sets can be deleted or paused). However, it carries high severity because misconfiguration of targeting, budget, or billing could lead to unintended ad spend. The dry-run default reduces risk but the live mode can commit real advertising resources.

From the tool's definition 'Create a Meta ad set under a campaign with targeting, budget, schedule, billing event, and optimization goal. Defaults to status=PAUSED. Dry-run by default.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

meta.adsets.create Rate-limited

meta.adsets.create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta.adsets.create": {
      "limits": [
        {
          "counter": "meta.adsets.create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ads, so you can run agents against it safely.

FAQ

Questions about meta.adsets.create

What does the meta.adsets.create tool do? +

Create a Meta ad set under a campaign with targeting, budget, schedule, billing event, and optimization goal. Defaults to status=PAUSED. Dry-run by default. The targeting object is passed through to Meta verbatim — see Meta. It is categorised as a Write tool in the Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on meta.adsets.create? +

Register the Ads MCP server in PolicyLayer and add a rule for meta.adsets.create: 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 Ads. Nothing to install.

What risk level is meta.adsets.create? +

meta.adsets.create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit meta.adsets.create? +

Yes. Add a rate_limit block to the meta.adsets.create 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.

How do I block meta.adsets.create completely? +

Set action: deny in the PolicyLayer policy for meta.adsets.create. 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.

What MCP server provides meta.adsets.create? +

meta.adsets.create is provided by the Ads MCP server (manlikemuneeb/ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.