factory_retry_review
先用 factory_diagnose_run 诊断，再绑定返回的 sourceFingerprint 执行一次有界补评。仅补 timeout/invalid-response 步骤，不重新生成业务输出，不改变原 run/batch 认证或采纳资格。每条运行最多一次、每回合最多三次并占运行额度；实验引用运行拒绝旁路补评。取消不自动重试，model-error 先排查，内容未达标应改业务提示词。必须显式提供调用、传输尝试和毫秒耗时预算，预算不足以覆盖失败步骤则拒绝。
This record as markdown: /tools/dutydeck/factory-retry-review.md
What factory_retry_review does on DutyDeck
AI agents invoke factory_retry_review 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_retry_review is rated High
factory_retry_review 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_retry_review 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_retry_review, this is the rule to start with:
factory_retry_review 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_retry_review call is checked against it from then on.
Questions about factory_retry_review
先用 factory_diagnose_run 诊断，再绑定返回的 sourceFingerprint 执行一次有界补评。仅补 timeout/invalid-response 步骤，不重新生成业务输出，不改变原 run/batch 认证或采纳资格。每条运行最多一次、每回合最多三次并占运行额度；实验引用运行拒绝旁路补评。取消不自动重试，model-error 先排查，内容未达标应改业务提示词。必须显式提供调用、传输尝试和毫秒耗时预算，预算不足以覆盖失败步骤则拒绝。. 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_retry_review: 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_retry_review 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_retry_review 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_retry_review. 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_retry_review 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