ads_orders

Every Rokha Ads campaign the caller owns (board spots included), with status, recalls and serves, the /word, and what's still owed. Requires Authorization: Bearer <JWT>.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/ads-orders.md

WHAT IT DOES

What ads_orders does on Rokha

AI agents call ads_orders 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.

RISK

Why ads_orders is rated Low

Tool queries advertising campaign and financial data without modifying it, but exposes sensitive billing information.

From the tool's definition retrieves Ads campaign status, recalls, serves, and billing data owned by caller

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ads_orders 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_orders, this is the rule to start with:

ads_orders Allowed

ads_orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ads_orders": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every ads_orders call is checked against it from then on.

FAQ

Questions about ads_orders

What does the ads_orders tool do? +

Every Rokha Ads campaign the caller owns (board spots included), with status, recalls and serves, the /word, and what's still owed. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ads_orders? +

Register the Rokha MCP server in PolicyLayer and add a rule for ads_orders: 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.

What risk level is ads_orders? +

ads_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ads_orders? +

Yes. Add a rate_limit block to the ads_orders 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.

How do I block ads_orders completely? +

Set action: deny in the PolicyLayer policy for ads_orders. 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.

What MCP server provides ads_orders? +

ads_orders 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

shopify_get_orders on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →