tag_work_item_criterion_staging_only
Say WHY one acceptance criterion cannot be checked locally, or clear that tag. Some criteria genuinely cannot be: a production provider with no local credential, a packaged installer, the pilot Mac, prod-only configuration. Without this the local gate would be unsatisfiable for those cards — and ...
This record as markdown: /tools/adrata-adrata-mcp/tag-work-item-criterion-staging-only.md
What tag_work_item_criterion_staging_only does on Adrata
AI agents call tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only is rated Critical
An AI agent that decides to call tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only, this is the rule to start with:
tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only call is checked against it from then on.
Questions about tag_work_item_criterion_staging_only
Say WHY one acceptance criterion cannot be checked locally, or clear that tag. Some criteria genuinely cannot be: a production provider with no local credential, a packaged installer, the pilot Mac, prod-only configuration. Without this the local gate would be unsatisfiable for those cards — and an unsatisfiable control does not fail closed, it gets routed around. It is a REASON, never a boolean, so the exemption is something a reviewer can disagree with. Pass \. 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 tag_work_item_criterion_staging_only: 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.
tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only 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 tag_work_item_criterion_staging_only. 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.
tag_work_item_criterion_staging_only 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