Activate a disabled TikTok campaign so it starts running. Requires Pro plan or higher ($69/mo).
AI agents invoke enable_tiktok_campaign to trigger actions in Agent1st Ads. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Enabling a campaign causes it to start running and spending ad budget on TikTok. While it doesn't directly move money in a transactional sense, it activates financial expenditure by resuming ad delivery. It is an external operation with real-world consequences (ad spend begins immediately).
From the tool's definition 'Activate a disabled TikTok campaign so it starts running' — triggers external ad campaign operations that cause real-world ad delivery and spend.
Attacks that exploit this kind of access
Activate a disabled TikTok campaign so it starts running. Requires Pro plan or higher ($69/mo). It is categorised as a Execute tool in the Agent1st Ads MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent1st Ads MCP server in PolicyLayer and add a rule for enable_tiktok_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 Agent1st Ads. Nothing to install.
enable_tiktok_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the enable_tiktok_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 enable_tiktok_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.
enable_tiktok_campaign is provided by the Agent1st Ads MCP server (nolas-shadow/agent1st-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 →