registry_adopt
The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_search; the listing must carry a metadata.rig skeleton). Idempotent per (you, listing) — re-adopting refreshes the copy from the listing. Returns rig_id + th...
This record as markdown: /tools/ai-rokha-rokha/registry-adopt.md
What registry_adopt does on Rokha
AI agents invoke registry_adopt to trigger actions in Rokha. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
external_id | string | Yes | the listing's external_id (e.g. 'rig-template-solwatch-audit') |
provider_id | string | Yes | the listing's provider (e.g. 'rokha') |
Parameters from the server's own tool schema.
Why registry_adopt is rated High
Tool executes arbitrary published rigs with user-controlled inputs, runs code in user's name/allowance context.
From the tool's definition materialize runnable copy, execute it over run stream, runs bill YOUR allowance
Attacks that exploit this kind of access
The rule that runs registry_adopt 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 registry_adopt, this is the rule to start with:
registry_adopt stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 registry_adopt call is checked against it from then on.
Questions about registry_adopt
The select → input → run door: materialize YOUR OWN runnable copy of any published rig listing (find provider_id + external_id via registry_search; the listing must carry a metadata.rig skeleton). Idempotent per (you, listing) — re-adopting refreshes the copy from the listing. Returns rig_id + the rig's declared input; then execute it over the run stream with user_context.rig_id and run_input. Runs bill YOUR allowance, never the creator's. A run whose final output carries a top-level rokha_app object (title/subject/verdict/score/metrics/sections/actions — the RokhaApp schema in /api/schema) renders as a native dashboard on Rokha's app surfaces; a ./rokha-app.html artifact saved by the run renders as its live app. Requires Authorization: Bearer <JWT>. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
registry_adopt accepts 2 parameters: external_id, provider_id. Required: external_id, provider_id. 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 registry_adopt: 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.
registry_adopt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the registry_adopt 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 registry_adopt. 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.
registry_adopt 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