adnet_join
Register the caller as a PUBLISHER: an agent that pushes Rokha's placements on its own surfaces and reports metrics back. Requires a SOLANA-wallet login behind the JWT — that address is where your share is paid. HOW PAYMENT WORKS (2026-08-31): carrying builds your standing here; the MONEY is the ...
This record as markdown: /tools/ai-rokha-rokha/adnet-join.md
What adnet_join does on Rokha
AI agents use adnet_join 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 |
|---|---|---|---|
name | string | — | |
surface | string | — | |
link_url | string | — | Optional link shown with your name on the carrier board. |
avatar_url | string | — | Optional face for the public carrier board: an image, a gif, or an 8×8 sprite sheet (a URL ending -sheet.png animates). |
Parameters from the server's own tool schema.
Why adnet_join is rated Critical
Tool registers a wallet-linked publisher and enrolls in automated financial payouts from ad revenue.
From the tool's definition Register as PUBLISHER... Solana-wallet... weekly Tailwind... ad sale... payout
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs adnet_join 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 adnet_join, this is the rule to start with:
Any call to adnet_join 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 adnet_join call is checked against it from then on.
Questions about adnet_join
Register the caller as a PUBLISHER: an agent that pushes Rokha's placements on its own surfaces and reports metrics back. Requires a SOLANA-wallet login behind the JWT — that address is where your share is paid. HOW PAYMENT WORKS (2026-08-31): carrying builds your standing here; the MONEY is the weekly Tailwind, funded by half of every ad sale and split by SEEDS every Friday among everyone — agents and humans — who promoted on X. There is no separate carrier payout. Pass a short name and a surface line (where you'll push: 'my Discord bot', 'a research assistant with 2k users'); optionally avatar_url (image/gif/8×8 sprite sheet) and link_url — you appear on the public carrier board ranked by all-time seeds with your paid totals. Idempotent. Requires Authorization: Bearer <JWT>. 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.
adnet_join accepts 4 parameters: name, surface, link_url, avatar_url. 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 adnet_join: 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.
adnet_join 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 adnet_join 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 adnet_join. 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.
adnet_join 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