product_set
Requires a JWT. Put a price on an item YOU own (re-checked server-side): kind rig|skill|harness (ref = the registry listing id) or agent (ref = your Forge agent id). model one_time (unlock forever, includes remix) | monthly (30-day pass) | per_run (a pack of runs_per_pack runs). price_cents 100–1...
This record as markdown: /tools/ai-rokha-rokha/product-set.md
What product_set does on Rokha
AI agents use product_set 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 |
|---|---|---|---|
ref | string | Yes | |
kind | string | Yes | |
model | string | Yes | |
active | boolean | — | |
price_cents | integer | Yes | |
runs_per_pack | integer | — |
Parameters from the server's own tool schema.
Why product_set is rated Critical
Tool sets pricing and financial terms for items, directly committing financial obligations and monetization.
From the tool's definition Put a price on an item, price_cents, earn 80% of every sale
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs product_set 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_set, this is the rule to start with:
Any call to product_set 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 product_set call is checked against it from then on.
Questions about product_set
Requires a JWT. Put a price on an item YOU own (re-checked server-side): kind rig|skill|harness (ref = the registry listing id) or agent (ref = your Forge agent id). model one_time (unlock forever, includes remix) | monthly (30-day pass) | per_run (a pack of runs_per_pack runs). price_cents 100–1000000. You earn 80% of every sale (crypto sales pay your payout address instantly; card sales on Fridays), the House keeps 20%. active:false takes the price off (free again). 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.
product_set accepts 6 parameters: ref, kind, model, active, price_cents, runs_per_pack. Required: ref, kind, model, price_cents. 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_set: 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_set 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 product_set 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_set. 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_set 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