registry_publish

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

Medium RISK CLASS

Category Write

Parameters 93 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/registry-publish.md

WHAT IT DOES

What registry_publish does on Rokha

AI agents use registry_publish to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.

Parameter	Type	Required	Description
`name`	string	Yes	kebab-case slug, ≤64 chars
`tags`	array	—
`title`	string	—	display name (defaults to the slug)
`version`	string	—
`homepage`	string	—
`metadata`	object	—	the artifact: skill_md / harness / rig (≤200KB)
`source_id`	string	—	UUID of the rig/harness/skill this listing is published FROM. Pass it whenever you have it: the server verifies you own that record, stamps it on the listing, a
`description`	string	Yes	what it does (≤4000 chars) — this is the discovery text
`listing_type`	string	Yes

Parameters from the server's own tool schema.

RISK

Why registry_publish is rated Medium

Creates or modifies registry listings reversibly; high blast radius if agent publishes malicious skills under another identity.

From the tool's definition Publish or update YOUR listing in the Rokha Registry

Attacks that exploit this kind of access

RECOMMENDED RULE

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

registry_publish Rate-limited

registry_publish stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "registry_publish": {
      "limits": [
        {
          "counter": "registry_publish_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about registry_publish

What does the registry_publish tool do? +

Publish (or update) YOUR listing in the Rokha Registry so anyone — human or agent — can find and use it. Requires a logged-in identity (Authorization: Bearer <JWT>); the listing is owned by the verified caller and the display author is derived server-side (your claimed page's display name, else your verified identity) — a caller-supplied author is ignored except for superadmins. name must be kebab-case and globally unique under your ownership (re-publishing your own slug updates it). listing_type: 'skill' (a SKILL.md in metadata.skill_md), 'harness' (a harness config in metadata.harness), or 'rig' (a rig skeleton in metadata.rig). 'server' is accepted as a legacy alias for a harness publish. Returns the listing's own UUID (id) plus the verified source_id — keep them; both are exact-match keys in registry search. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does registry_publish accept? +

registry_publish accepts 9 parameters: name, tags, title, version, homepage, metadata, source_id, description, listing_type. Required: name, description, listing_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on registry_publish? +

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

registry_publish is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit registry_publish? +

Yes. Add a rate_limit block to the registry_publish 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 registry_publish completely? +

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

registry_publish 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →