rig_edge
Wire or unwire ONE edge between two EXISTING blocks of a canvas rig — 'connect the fetch step to the judge', 'route the critique back to revise when it says REVISE', 'disconnect A from B'. Identify both ends by node id, label, skill name, or 1-based position. Add guard ({source, op, value?}) to m...
This record as markdown: /tools/ai-rokha-rokha/rig-edge.md
What rig_edge does on Rokha
AI agents use rig_edge 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 |
|---|---|---|---|
to | string | Yes | Destination block: same identifiers |
from | string | Yes | Source block: node id, label, skill name, or 1-based position |
kind | string | — | 'data' (default) | 'control' | 'conditional' (implied when guard is set) |
guard | object | — | Take this edge ONLY when the condition holds — {source, op, value?}. `source` is a `{{node.port}}` channel ref; `op` = eq | not_eq | contains | gt | gte | lt | |
remove | boolean | — | true = drop the from→to edge instead of adding one |
rig_id | string | Yes | UUID of the rig (rig_search finds it) |
wallet_address | string | Yes | Owner scope |
Parameters from the server's own tool schema.
Why rig_edge is rated Medium
Modifies canvas topology by connecting or disconnecting nodes; reversible graph edits.
From the tool's definition Wire or unwire ONE edge between two EXISTING blocks
Risk signalsHigh parameter count (10 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rig_edge 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_edge, this is the rule to start with:
rig_edge 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every rig_edge call is checked against it from then on.
Questions about rig_edge
Wire or unwire ONE edge between two EXISTING blocks of a canvas rig — 'connect the fetch step to the judge', 'route the critique back to revise when it says REVISE', 'disconnect A from B'. Identify both ends by node id, label, skill name, or 1-based position. Add guard ({source, op, value?}) to make the edge a CONDITIONAL route — how a loop gets its exit condition on a stateful_graph. remove: true drops the from→to edge instead. Re-wiring an edge that already exists UPDATES its kind/guard in place. Returns the fresh block-by-block summary incl. the full edge topology; the Builder canvas updates live. (rig_node_add's after wires only at creation — this is the tool for every rewiring after that.). 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.
rig_edge accepts 7 parameters: to, from, kind, guard, remove, rig_id, wallet_address. Required: to, from, 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_edge: 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_edge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rig_edge 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_edge. 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_edge 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.
This server
Across the catalogue