rig_node_add

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

Medium RISK CLASS

Category Write

Parameters 43 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-add.md

WHAT IT DOES

What rig_node_add does on Rokha

AI agents use rig_node_add 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
`node`	object	Yes	The block, same fields as a rig_author node: {skill?, sub_rig?, label?, instruction?, doc_input?, endpoint?, tool?, params?, url?, method?, data_op?, data_key?,
`after`	string	—	Wire the new block after THIS node (id, label, skill name, or 1-based position). Default: the current terminal block. 'none' = leave unwired.
`rig_id`	string	Yes	UUID of the rig (rig_search finds it; the Working Rig is usually the most recent)
`wallet_address`	string	Yes	Owner scope

Parameters from the server's own tool schema.

RISK

Why rig_node_add is rated Medium

Modifies workflow configuration reversibly by appending nodes; changes are editable and undoable within the system.

From the tool's definition Add ONE block (graph node) to a canvas rig — the granular edit for 'add a step that …'.

Risk signalsAccepts URL/endpoint input (node.endpoint) · High parameter count (30 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rig_node_add Rate-limited

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

FAQ

Questions about rig_node_add

What does the rig_node_add tool do? +

Add ONE block (graph node) to a canvas rig — the granular edit for 'add a step that …'. Appends and auto-wires an edge from the current last block (default), from after (a node id/label/position), or unwired with after='none' (a new parallel branch head). Node fields match rig_author's nodes. Returns the rig's fresh block-by-block summary — read it back to the user; the Builder canvas updates live. For whole-rig authoring use rig_author; this is the scalpel. 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_add accept? +

rig_node_add accepts 4 parameters: node, after, rig_id, wallet_address. Required: node, rig_id, wallet_address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rig_node_add? +

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

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

Can I rate-limit rig_node_add? +

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

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

rig_node_add 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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