Create an ad set inside a campaign. Defaults to status=PAUSED. WRITE OPERATION.
AI agents use create_adset to create or update resources in Claude Meta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Meta environment.
This tool creates new ad set configurations within Meta campaigns, which is a reversible write operation that modifies advertising account state. Classified as Write rather than Financial because it creates ad structures (not direct monetary transactions), though it could facilitate financial harm if misused to create high-budget ad sets.
From the tool's definition Tool name is 'create_adset' and description states 'Create an ad set inside a campaign' and explicitly labels this a 'WRITE OPERATION'. Creates new advertising structures within Meta Ads campaigns.
Attacks that exploit this kind of access
Create an ad set inside a campaign. Defaults to status=PAUSED. WRITE OPERATION. It is categorised as a Write tool in the Claude Meta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Meta MCP server in PolicyLayer and add a rule for create_adset: 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 Claude Meta. Nothing to install.
create_adset 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 create_adset 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 create_adset. 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.
create_adset is provided by the Claude Meta MCP server (maxx3250/claude-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 →