delete_work_item_acceptance_criterion
PERMANENTLY REMOVE one acceptance criterion from a card, taking its history with it. Reach for this ONLY when a criterion is unsatisfiable BY CONSTRUCTION — when no evidence any reviewer could gather would ever discharge it. That is not a high bar being enforced; it is a card that can never leave...
This record as markdown: /tools/adrata-adrata-mcp/delete-work-item-acceptance-criterion.md
What delete_work_item_acceptance_criterion does on Adrata
AI agents call delete_work_item_acceptance_criterion 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 delete_work_item_acceptance_criterion is rated Critical
An AI agent that decides to call delete_work_item_acceptance_criterion 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_work_item_acceptance_criterion 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 delete_work_item_acceptance_criterion, this is the rule to start with:
delete_work_item_acceptance_criterion 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 delete_work_item_acceptance_criterion call is checked against it from then on.
Questions about delete_work_item_acceptance_criterion
PERMANENTLY REMOVE one acceptance criterion from a card, taking its history with it. Reach for this ONLY when a criterion is unsatisfiable BY CONSTRUCTION — when no evidence any reviewer could gather would ever discharge it. That is not a high bar being enforced; it is a card that can never leave its gate, and it costs a full pass every time a lane draws it and discovers why. TWO SHAPES QUALIFY, and both were measured on this board: GATE-AS-CRITERION. Its subject is the exit condition of the whole gate or the whole board rather than this card. 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 delete_work_item_acceptance_criterion: 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.
delete_work_item_acceptance_criterion 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 delete_work_item_acceptance_criterion 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 delete_work_item_acceptance_criterion. 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.
delete_work_item_acceptance_criterion 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