factory_advance_experiment
Run exactly the next split within the same 3 comparison rounds and 60 run units used by other tools. Only after optimization may candidatePrompt be revised once. Validation freezes it; failures stop later calls. Never automatically adopt or overwrite a draft.
This record as markdown: /tools/dutydeck/factory-advance-experiment.md
What factory_advance_experiment does on DutyDeck
AI agents invoke factory_advance_experiment 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_advance_experiment is rated High
factory_advance_experiment 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_advance_experiment 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_advance_experiment, this is the rule to start with:
factory_advance_experiment 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_advance_experiment call is checked against it from then on.
Questions about factory_advance_experiment
Run exactly the next split within the same 3 comparison rounds and 60 run units used by other tools. Only after optimization may candidatePrompt be revised once. Validation freezes it; failures stop later calls. Never automatically adopt or overwrite a draft. 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_advance_experiment: 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_advance_experiment 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_advance_experiment 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_advance_experiment. 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_advance_experiment 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