adspace_bid
LEGACY — the AdSpace spots board (planet/moon) is RETIRED as a public surface; placement on Rokha is a Rokha Network membership now (rokha.ai/network#join, monthly plans). This door still answers for holders already on the old board. Requires Authorization: Bearer <JWT> from a Solana-wallet login.
This record as markdown: /tools/ai-rokha-rokha/adspace-bid.md
What adspace_bid does on Rokha
AI agents use adspace_bid 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 | https link to what you're promoting |
slug | string | — | your /word (optional; made from the title if empty) |
tier | string | Yes | |
when | string | — | when Rokha should recommend you — e.g. 'someone asks about on-chain analytics' (what the agent matches against; be concrete) |
pitch | string | Yes | one line, 10–200 chars |
title | string | Yes | the name, 3–60 chars |
bio_md | string | — | long-form bio for your ad page — markdown, pretty-printed, up to 8,000 chars (optional) |
logo_url | string | — | https image/logo (square, ≥256×256) |
amount_usd | integer | Yes | whole USDC, at or above the price to take a spot |
banner_url | string | — | https wide banner for your ad page (~1500×500; optional) |
Parameters from the server's own tool schema.
Why adspace_bid is rated Critical
Tool manages advertising placement bids and financial membership commitments.
From the tool's definition bid, monthly plans, placement, AdSpace, membership
Risk signalsAccepts URL/endpoint input (url) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs adspace_bid 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 adspace_bid, this is the rule to start with:
Any call to adspace_bid 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 adspace_bid call is checked against it from then on.
Questions about adspace_bid
LEGACY — the AdSpace spots board (planet/moon) is RETIRED as a public surface; placement on Rokha is a Rokha Network membership now (rokha.ai/network#join, monthly plans). This door still answers for holders already on the old board. 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.
adspace_bid accepts 10 parameters: url, slug, tier, when, pitch, title, bio_md, logo_url, amount_usd, banner_url. Required: url, tier, pitch, title, amount_usd. 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 adspace_bid: 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.
adspace_bid 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 adspace_bid 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 adspace_bid. 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.
adspace_bid 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