run_decision_cycle
Runs a full Decision Twin negotiation cycle for a raw manufacturing event object. Unlike run_decision_twin_orchestrator (flat params), this accepts the event object directly and returns the complete orchestrator state, including the full agent trace and negotiation history.
This record as markdown: /tools/nitrostack/run-decision-cycle.md
What run_decision_cycle does on Nitrostack
AI agents invoke run_decision_cycle to trigger actions in Nitrostack. 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 run_decision_cycle is rated High
Executes decision-making workflow cycles with orchestrator state management; effects depend on input event structure.
From the tool's definition Runs a full Decision Twin negotiation cycle for raw manufacturing event object
Attacks that exploit this kind of access
The rule that runs run_decision_cycle safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_decision_cycle, this is the rule to start with:
run_decision_cycle 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 Nitrostack, apply this rule, and every run_decision_cycle call is checked against it from then on.
Questions about run_decision_cycle
Runs a full Decision Twin negotiation cycle for a raw manufacturing event object. Unlike run_decision_twin_orchestrator (flat params), this accepts the event object directly and returns the complete orchestrator state, including the full agent trace and negotiation history. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nitrostack MCP server in PolicyLayer and add a rule for run_decision_cycle: 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 Nitrostack. Nothing to install.
run_decision_cycle 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 run_decision_cycle 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 run_decision_cycle. 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.
run_decision_cycle is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue