factory_run_step
Run ONE prompt step with the input you provide, then automatically assess its output against this run’s fixed acceptance rules. Returns traces plus review (criterion evidence, metrics, suggestions and pass/unknown/fail). Assessment is limited to this step; it does not certify the whole scene. Use...
This record as markdown: /tools/dutydeck/factory-run-step.md
What factory_run_step does on DutyDeck
AI agents invoke factory_run_step to trigger actions in DutyDeck. 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 factory_run_step is rated High
factory_run_step 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 factory_run_step safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For factory_run_step, this is the rule to start with:
factory_run_step 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 DutyDeck, apply this rule, and every factory_run_step call is checked against it from then on.
Questions about factory_run_step
Run ONE prompt step with the input you provide, then automatically assess its output against this run’s fixed acceptance rules. Returns traces plus review (criterion evidence, metrics, suggestions and pass/unknown/fail). Assessment is limited to this step; it does not certify the whole scene. Use this to verify a prompt change yourself instead of asking the human to run it. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DutyDeck MCP server in PolicyLayer and add a rule for factory_run_step: 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 DutyDeck. Nothing to install.
factory_run_step 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 factory_run_step 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 factory_run_step. 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.
factory_run_step is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
Across the catalogue