ads_order
Buy placement inside the agent by the week — this IS the ORBIT tier: an active weekly order puts you in the AdSpace board's orbit ring (unlimited, no bidding) and names you in the weekly Rokha AdSpace Promotions roundup post. memory = Rokha (and every agent on the team) recommends you when an ask...
This record as markdown: /tools/ai-rokha-rokha/ads-order.md
What ads_order does on Rokha
AI agents use ads_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 | |
slug | string | — | your /word (optional) |
when | string | — | when Rokha should recommend you |
pitch | string | Yes | |
title | string | Yes | |
weeks | integer | — | |
package | string | Yes |
Parameters from the server's own tool schema.
Why ads_order is rated Critical
Tool directly purchases ad placements and processes financial transactions in USDC.
From the tool's definition Buy placement... weekly order... payment instructions... exact USDC
Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ads_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 ads_order, this is the rule to start with:
Any call to ads_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 ads_order call is checked against it from then on.
Questions about ads_order
Buy placement inside the agent by the week — this IS the ORBIT tier: an active weekly order puts you in the AdSpace board's orbit ring (unlimited, no bidding) and names you in the weekly Rokha AdSpace Promotions roundup post. memory = Rokha (and every agent on the team) recommends you when an ask matches your when, always labelled sponsored; slot = the /ad card on every agent lane; bundle = both. Prices from GET /api/ads/packages; the full per-tier offer (incl. the auction PLANET/MOON perks) rides GET /api/adspace → promotions. Returns the order + payment instructions (exact USDC from the caller's login wallet; Solana Pay URI). Goes live on finality; your /word is made from the title if you don't pass one. Requires Authorization: Bearer <JWT> from a Solana-wallet login. 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.
ads_order accepts 7 parameters: url, slug, when, pitch, title, weeks, package. Required: url, pitch, title, package. 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_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.
ads_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 ads_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 ads_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.
ads_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