campaign_claim
Requires a JWT. Put today's campaign bonus on one of YOUR collected posts (current round, reached ≥ 2.0 X-weighted, not copied or deleted, carrying the campaign's tag + words). Already claimed that day? It MOVES to this post — still one bonus a day. Optional campaign = a slug from campaigns.
This record as markdown: /tools/ai-rokha-rokha/campaign-claim.md
What campaign_claim does on Rokha
AI agents use campaign_claim to commit financial operations through Rokha, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | The X post id (digits) of your own post |
campaign | string | — | optional campaign slug |
Parameters from the server's own tool schema.
Why campaign_claim is rated Critical
Claims or moves a financial campaign bonus, committing a financial reward action.
From the tool's definition campaign bonus...claimed...MOVES to this post
Attacks that exploit this kind of access
The rule that runs campaign_claim 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 campaign_claim, this is the rule to start with:
Any call to campaign_claim is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every campaign_claim call is checked against it from then on.
Questions about campaign_claim
Requires a JWT. Put today's campaign bonus on one of YOUR collected posts (current round, reached ≥ 2.0 X-weighted, not copied or deleted, carrying the campaign's tag + words). Already claimed that day? It MOVES to this post — still one bonus a day. Optional campaign = a slug from campaigns. It is categorised as a Financial tool in the Rokha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
campaign_claim accepts 2 parameters: post_id, campaign. Required: post_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 campaign_claim: 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.
campaign_claim is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the campaign_claim 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 campaign_claim. 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.
campaign_claim 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.
Across the catalogue