ads_campaign_pause

Stop a live campaign from being recalled or served (the clock keeps running). Requires Authorization: Bearer <JWT>.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/ads-campaign-pause.md

WHAT IT DOES

What ads_campaign_pause does on Rokha

AI agents call ads_campaign_pause to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`id`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why ads_campaign_pause is rated Low

Even though ads_campaign_pause only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ads_campaign_pause 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_pause, this is the rule to start with:

ads_campaign_pause Allowed

ads_campaign_pause is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ads_campaign_pause": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every ads_campaign_pause call is checked against it from then on.

FAQ

Questions about ads_campaign_pause

What does the ads_campaign_pause tool do? +

Stop a live campaign from being recalled or served (the clock keeps running). Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does ads_campaign_pause accept? +

ads_campaign_pause accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ads_campaign_pause? +

Register the Rokha MCP server in PolicyLayer and add a rule for ads_campaign_pause: 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.

What risk level is ads_campaign_pause? +

ads_campaign_pause is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ads_campaign_pause? +

Yes. Add a rate_limit block to the ads_campaign_pause 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.

How do I block ads_campaign_pause completely? +

Set action: deny in the PolicyLayer policy for ads_campaign_pause. 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.

What MCP server provides ads_campaign_pause? +

ads_campaign_pause 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →