rig_node_update

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

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/rig-node-update.md

WHAT IT DOES

What rig_node_update does on Rokha

AI agents use rig_node_update 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
`url`	string	—
`node`	string	Yes	Which block: node id, label, skill name, or 1-based position ('2')
`tool`	string	—
`label`	string	—
`model`	string	—
`skill`	string	—	Re-bind the block to this registry skill (optional)
`method`	string	—
`params`	object	—
`rig_id`	string	Yes	UUID of the rig
`data_op`	string	—
`expects`	string	—	What this step expects from upstream, in plain words
`headers`	object	—	Extra HTTP headers for a `url` fetch.

Parameters from the server's own tool schema.

RISK

Why rig_node_update is rated Medium

Modifies canvas rig node configuration reversibly; affects execution flow but not destructively.

From the tool's definition Configure block in place, change instruction, point at endpoint, MERGE tweaking.

Risk signalsAccepts URL/endpoint input (endpoint) · High parameter count (24 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rig_node_update Rate-limited

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

FAQ

Questions about rig_node_update

What does the rig_node_update tool do? +

Configure ONE block (graph node) of a canvas rig in place — 'change step 2's instruction', 'point that block at a live endpoint', 'pin Sonnet on the judge step'. Identify the block by id/label/skill/position; pass only the fields to change (rig_author's node fields) — a MERGE, so tweaking the instruction never wipes a wired endpoint. skill re-resolves the registry binding. The block keeps its id, edges, and canvas position. Returns the fresh block summary; the Builder canvas updates live. 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 rig_node_update accept? +

rig_node_update accepts 12 parameters: url, node, tool, label, model, skill, method, params, rig_id, data_op, expects, headers. Required: node, rig_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rig_node_update? +

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

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

Can I rate-limit rig_node_update? +

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

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

rig_node_update 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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