rc_sequence_to_user_workflow
Mirror an rc_sequence into user_workflows so the customer can edit / run / schedule it from the onork-app /dashboard/automations surface. Produces a node/edge graph compatible with the existing flow-step mapper. Returns the user_workflows row id (uuid). The customer
This record as markdown: /tools/io-github-0nork-0nmcp/rc-sequence-to-user-workflow.md
What rc_sequence_to_user_workflow does on 0nmcp
AI agents invoke rc_sequence_to_user_workflow to trigger actions in 0nmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rc_sequence_to_user_workflow is rated High
rc_sequence_to_user_workflow triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs rc_sequence_to_user_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rc_sequence_to_user_workflow, this is the rule to start with:
rc_sequence_to_user_workflow stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every rc_sequence_to_user_workflow call is checked against it from then on.
Questions about rc_sequence_to_user_workflow
Mirror an rc_sequence into user_workflows so the customer can edit / run / schedule it from the onork-app /dashboard/automations surface. Produces a node/edge graph compatible with the existing flow-step mapper. Returns the user_workflows row id (uuid). The customer. It is categorised as a Execute tool in the 0nmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 0n MCP server in PolicyLayer and add a rule for rc_sequence_to_user_workflow: 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 0nmcp. Nothing to install.
rc_sequence_to_user_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rc_sequence_to_user_workflow 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 rc_sequence_to_user_workflow. 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.
rc_sequence_to_user_workflow is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue