create_adset
AI agents use create_adset to create or update resources in KonQuest Meta Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KonQuest Meta Ads MCP environment.
Creating an ad set (a collection of ads in Meta Ads Manager) is a reversible Write operation—it creates data structures that can be modified or deleted. The blast radius is medium because misconfigured ad sets could waste ad budget, but the operation itself is not destructive, does not execute arbitrary code, and does not move money directly.
From the tool's definition Tool name 'create_adset' indicates creation of advertising campaign components. Sibling tools include 'create_campaign', 'create_ad_creative', and 'create_multi_asset_ad', establishing a pattern of Write operations.
Attacks that exploit this kind of access
create_adset. It is categorised as a Write tool in the KonQuest Meta Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KonQuest Meta Ads 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 KonQuest Meta Ads MCP. 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 KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-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 →