ads_campaign_update
Rewrite a live campaign's link, name, pitch, when line, /word or logo — the agent's memory re-syncs at once. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/ads-campaign-update.md
What ads_campaign_update does on Rokha
AI agents use ads_campaign_update to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | |
url | string | Yes | |
slug | string | — | |
when | string | — | |
pitch | string | Yes | |
title | string | Yes | |
logo_url | string | — |
Parameters from the server's own tool schema.
Why ads_campaign_update is rated Medium
Modifies live campaign data reversibly; high impact on active advertising operations and business metrics.
From the tool's definition Rewrite a live campaign's link, name, pitch, when line, word or logo
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs ads_campaign_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ads_campaign_update, this is the rule to start with:
ads_campaign_update 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every ads_campaign_update call is checked against it from then on.
Questions about ads_campaign_update
Rewrite a live campaign's link, name, pitch, when line, /word or logo — the agent's memory re-syncs at once. Requires Authorization: Bearer <JWT>. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ads_campaign_update accepts 7 parameters: id, url, slug, when, pitch, title, logo_url. Required: id, url, pitch, title. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for ads_campaign_update: 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 Rokha. Nothing to install.
ads_campaign_update 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 ads_campaign_update 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 ads_campaign_update. 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.
ads_campaign_update is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue