requeue_work_item_qa_after_fix
Clear a failed QA card’s waiting-for-fix flag only after a different exact build has been deployed and its relationship to the failed build has been checked. This does not claim or certify the card; it clears the resolved hold or failure handoff before a fresh independent QA pass. The clear reaso...
This record as markdown: /tools/adrata-adrata-mcp/requeue-work-item-qa-after-fix.md
What requeue_work_item_qa_after_fix does on Adrata
AI agents call requeue_work_item_qa_after_fix to permanently remove resources in Adrata, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why requeue_work_item_qa_after_fix is rated Critical
An AI agent that decides to call requeue_work_item_qa_after_fix doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Adrata is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs requeue_work_item_qa_after_fix safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For requeue_work_item_qa_after_fix, this is the rule to start with:
requeue_work_item_qa_after_fix is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every requeue_work_item_qa_after_fix call is checked against it from then on.
Questions about requeue_work_item_qa_after_fix
Clear a failed QA card’s waiting-for-fix flag only after a different exact build has been deployed and its relationship to the failed build has been checked. This does not claim or certify the card; it clears the resolved hold or failure handoff before a fresh independent QA pass. The clear reason durably records both SHAs and the fix/deployment reference. The worker must verify ancestry in source control before calling this tool; this endpoint rejects the unchanged SHA but does not pretend to be a Git ancestry oracle.${GOVERNED_NOTE}. It is categorised as a Destructive tool in the Adrata MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Adrata MCP server in PolicyLayer and add a rule for requeue_work_item_qa_after_fix: 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 Adrata. Nothing to install.
requeue_work_item_qa_after_fix is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the requeue_work_item_qa_after_fix 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 requeue_work_item_qa_after_fix. 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.
requeue_work_item_qa_after_fix is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
Across the catalogue