rig_node_remove
Remove ONE block (graph node) from a canvas rig — 'delete step 2' / 'drop the summarize block'. Identify the block by node id, label, bound-skill name, or 1-based position. The chain HEALS: every upstream re-wires to every downstream, so deleting a middle block never severs the flow. Returns the ...
This record as markdown: /tools/ai-rokha-rokha/rig-node-remove.md
What rig_node_remove does on Rokha
AI agents call rig_node_remove to permanently remove resources in Rokha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
node | string | Yes | Which block: node id, label, skill name, or 1-based position ('2') |
rig_id | string | Yes | UUID of the rig |
wallet_address | string | Yes | Owner scope |
Parameters from the server's own tool schema.
Why rig_node_remove is rated Critical
Permanently removes a graph node; though chain heals, the deletion itself is irreversible.
From the tool's definition Remove ONE block...delete step...drop the summarize block
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rig_node_remove 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_remove, this is the rule to start with:
rig_node_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every rig_node_remove call is checked against it from then on.
Questions about rig_node_remove
Remove ONE block (graph node) from a canvas rig — 'delete step 2' / 'drop the summarize block'. Identify the block by node id, label, bound-skill name, or 1-based position. The chain HEALS: every upstream re-wires to every downstream, so deleting a middle block never severs the flow. Returns the fresh block summary; the Builder canvas updates live. It is categorised as a Destructive tool in the Rokha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
rig_node_remove accepts 3 parameters: node, 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.
Register the Rokha MCP server in PolicyLayer and add a rule for rig_node_remove: 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.
rig_node_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rig_node_remove 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 rig_node_remove. 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.
rig_node_remove 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