duplicate_campaign
AI agents use duplicate_campaign 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.
Based on the tool name, duplicating a campaign most likely creates a new copy of an existing campaign, which is a Write operation. However, the empty description lowers confidence. Given the server context (Meta Ads management with 57 campaign tools), duplicating a campaign could spawn new ad spend obligations, but without clear evidence of financial commitment it falls under Write.
From the tool's definition Tool name: duplicate_campaign; description is empty and uninformative.
Attacks that exploit this kind of access
duplicate_campaign. 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 duplicate_campaign: 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.
duplicate_campaign 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 duplicate_campaign 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 duplicate_campaign. 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.
duplicate_campaign 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 →