carry_order
No account needed. Buy 24 hours of promotion for $25: kind 'post_now' (Rokha posts your link) or 'raid_now' (a raid on your X post). Name the brand or tool (title) and the link (url); rail 'usdc' returns exact pay instructions. Next: carry_order_check with the reference.
This record as markdown: /tools/ai-rokha-rokha/carry-order.md
What carry_order does on Rokha
AI agents use carry_order 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 |
|---|---|---|---|
url | string | Yes | |
kind | string | Yes | |
rail | string | — | |
pitch | string | — | |
title | string | Yes | |
sponsor_x | string | — | |
payer_wallet | string | — |
Parameters from the server's own tool schema.
Why carry_order is rated Critical
Tool commits financial transactions, purchasing promotional services via USDC payment.
From the tool's definition Buy 24 hours of promotion for $25, pay instructions, usdc
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs carry_order 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 carry_order, this is the rule to start with:
Any call to carry_order 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 carry_order call is checked against it from then on.
Questions about carry_order
No account needed. Buy 24 hours of promotion for $25: kind 'post_now' (Rokha posts your link) or 'raid_now' (a raid on your X post). Name the brand or tool (title) and the link (url); rail 'usdc' returns exact pay instructions. Next: carry_order_check with the reference. 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.
carry_order accepts 7 parameters: url, kind, rail, pitch, title, sponsor_x, payer_wallet. Required: url, kind, 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 carry_order: 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.
carry_order 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 carry_order 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 carry_order. 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.
carry_order 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