page_rig_config

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

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/page-rig-config.md

WHAT IT DOES

What page_rig_config does on Rokha

AI agents use page_rig_config 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
`mode`	string	—
`slug`	string	Yes	the rig's slug (lowercase alnum + dashes — derived from its name)
`glyph`	string	—	hero glyph — an emoji or 1-2 chars ('' clears)
`accent`	string	—	page accent color as #rrggbb ('' clears)
`linked`	boolean	—
`gallery`	array	—	up to 6 https image URLs for the page's MEDIA panel (screenshots, brand art; [] clears)
`tagline`	string	—	product tagline shown under the rig name (≤140 chars; '' clears)
`featured`	boolean	—
`resident`	boolean	—	PRO: keep an always-on sandbox behind this page — instant live dashboard + warm interactions; owner-metered; fail-closed on tier lapse
`showcase`	boolean	—	show this rig on your public profile (and give it a config card) — opt-in; false hides it
`banner_url`	string	—	hero banner image — an https URL (the product's brand backdrop + share-card image; '' clears)
`hero_image`	string	—	hero PICTURE — a small data:image/... URI (≤260k chars; a 256px square, profile-photo style) replacing the glyph ('' clears)

Parameters from the server's own tool schema.

RISK

Why page_rig_config is rated Medium

Modifies published rig configuration and public profile display settings reversibly.

From the tool's definition config for ONE of your published rigs on your page

Risk signalsHigh parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

page_rig_config Rate-limited

page_rig_config 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": {
    "page_rig_config": {
      "limits": [
        {
          "counter": "page_rig_config_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 page_rig_config call is checked against it from then on.

FAQ

Questions about page_rig_config

What does the page_rig_config tool do? +

Owner config for ONE of your published rigs on your page: showcase (SHOW this rig on your public profile + give it a config card — opt-in; publishing alone no longer showcases a rig), mode ('builder' rig-detail view or 'app' app-output surface), featured (headline it in your SHOWCASE — single slot, featuring one un-features the rest), linked (mint the public /@handle/<slug> link — rigs do NOT get sub-pages unless you opt in), plus the sub-page's PRODUCT theme: tagline (≤140 chars under the rig name), accent (#rrggbb page accent color), glyph (an emoji/1-2 char hero mark). Pass an empty string to clear a theme field. Claim your page first. Requires Authorization: Bearer <JWT>. 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 page_rig_config accept? +

page_rig_config accepts 12 parameters: mode, slug, glyph, accent, linked, gallery, tagline, featured, resident, showcase, banner_url, hero_image. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on page_rig_config? +

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

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

Can I rate-limit page_rig_config? +

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

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

page_rig_config 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 →