product_get
Public. Is this item paid, and what does it cost? Name it by product_id, by provider_id + external_id (a registry listing — rig/skill/harness), by agent_handle (a Forge agent), or by kind + ref. Returns {product:{id,title,model: one_time|monthly|per_run, price_cents, runs_per_pack, checkout_url}}...
This record as markdown: /tools/ai-rokha-rokha/product-get.md
What product_get does on Rokha
AI agents call product_get 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
ref | string | — | |
kind | string | — | |
product_id | string | — | |
external_id | string | — | |
provider_id | string | — | |
agent_handle | string | — |
Parameters from the server's own tool schema.
Why product_get is rated Low
Tool queries product pricing data without executing payments or modifying state.
From the tool's definition Returns product pricing and cost information; no modifications or financial transactions executed.
Attacks that exploit this kind of access
The rule that runs product_get 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 product_get, this is the rule to start with:
product_get 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 product_get call is checked against it from then on.
Questions about product_get
Public. Is this item paid, and what does it cost? Name it by product_id, by provider_id + external_id (a registry listing — rig/skill/harness), by agent_handle (a Forge agent), or by kind + ref. Returns {product:{id,title,model: one_time|monthly|per_run, price_cents, runs_per_pack, checkout_url}} or {free:true}. A paid item answers any run with 402 purchase_required until you buy it: product_checkout (rail 'x402' or 'usdc' for agents — no browser; 'card' for a human). It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
product_get accepts 6 parameters: ref, kind, product_id, external_id, provider_id, agent_handle. 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 product_get: 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.
product_get 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 product_get 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 product_get. 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.
product_get 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