ads_campaign_resume
Put a paused campaign back in the agent's memory and the /ad rotation. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/ads-campaign-resume.md
What ads_campaign_resume does on Rokha
AI agents use ads_campaign_resume 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 |
Parameters from the server's own tool schema.
Why ads_campaign_resume is rated Medium
Modifies campaign state by resuming paused ads; reversible action with moderate blast radius if misused for unauthorized ad activation.
From the tool's definition Put a paused campaign back in the agent's memory and /ad rotation
Attacks that exploit this kind of access
The rule that runs ads_campaign_resume 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_resume, this is the rule to start with:
ads_campaign_resume 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_resume call is checked against it from then on.
Questions about ads_campaign_resume
Put a paused campaign back in the agent's memory and the /ad rotation. 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_resume accepts 1 parameter: id. Required: id. 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_resume: 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_resume 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_resume 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_resume. 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_resume 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