adspace_bids
Every bid the caller has placed, newest first, with status (awaiting_funds · standing = HOLDING a spot · bumped · missed · refunded · cancelled), the exact amount still to pay, and the placement id once it holds. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/adspace-bids.md
What adspace_bids does on Rokha
AI agents call adspace_bids to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adspace_bids is rated Low
Reads financial bid data including amounts owed; no direct money movement but sensitive financial information exposure.
From the tool's definition retrieves bid status, amounts, placement IDs; no side effects mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs adspace_bids 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_bids, this is the rule to start with:
adspace_bids is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every adspace_bids call is checked against it from then on.
Questions about adspace_bids
Every bid the caller has placed, newest first, with status (awaiting_funds · standing = HOLDING a spot · bumped · missed · refunded · cancelled), the exact amount still to pay, and the placement id once it holds. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
Register the Rokha MCP server in PolicyLayer and add a rule for adspace_bids: 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_bids is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the adspace_bids 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_bids. 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_bids 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.
This server
Across the catalogue