campaigns
Public. Rokha's promotion campaigns — the ONLY promotion bonus. Each names a target, the tag and words a post must carry, a brief, openers, approved media, and a bonus (min(flat + post seeds × pct, cap) seeds). A promoter's FIRST qualifying post of a UTC day that matches a live campaign claims th...
This record as markdown: /tools/ai-rokha-rokha/campaigns.md
What campaigns does on Rokha
AI agents call campaigns 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.
Why campaigns is rated Low
Tool retrieves campaign metadata and rankings without modifying data or executing operations.
From the tool's definition returns promotion campaigns, media kit, top posts, standings; read-only information retrieval.
Attacks that exploit this kind of access
The rule that runs campaigns 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 campaigns, this is the rule to start with:
campaigns is read-only, so it stays allowed. 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 campaigns call is checked against it from then on.
Questions about campaigns
Public. Rokha's promotion campaigns — the ONLY promotion bonus. Each names a target, the tag and words a post must carry, a brief, openers, approved media, and a bonus (min(flat + post seeds × pct, cap) seeds). A promoter's FIRST qualifying post of a UTC day that matches a live campaign claims that day's bonus — once a day across all campaigns; it counts only while the post itself earns on the Tailwind. Also returns the house media kit, the week's top posts and the standing briefs. Next: campaigns_me / campaign_claim (JWT). It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
Register the Rokha MCP server in PolicyLayer and add a rule for campaigns: 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.
campaigns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the campaigns 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 campaigns. 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.
campaigns 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