record_work_item_qa_failure_and_release

SERVERAdrata SOURCE@adrata/adrata-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/record-work-item-qa-failure-and-release.md

WHAT IT DOES

What record_work_item_qa_failure_and_release does on Adrata

AI agents invoke record_work_item_qa_failure_and_release to trigger actions in Adrata. 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.

RISK

Why record_work_item_qa_failure_and_release is rated High

record_work_item_qa_failure_and_release 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_work_item_qa_failure_and_release 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 record_work_item_qa_failure_and_release, this is the rule to start with:

record_work_item_qa_failure_and_release Rate-limited

record_work_item_qa_failure_and_release 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_work_item_qa_failure_and_release": {
      "limits": [
        {
          "counter": "record_work_item_qa_failure_and_release_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every record_work_item_qa_failure_and_release call is checked against it from then on.

FAQ

Questions about record_work_item_qa_failure_and_release

What does the record_work_item_qa_failure_and_release tool do? +

Durably record why the current QA pass cannot proceed, then safely release the process-private lease without moving the card. Three dispositions, and only one of them flags: - failed_criterion: the criterion is marked UNMET (un-ticked) and a comment records what failed, on which build, and what to check. NO FLAG: the unmet criterion is the finding, the card stays claimable, and a later pass that verifies the criterion again is the fix. This is one governed recovery recipe, not a new bug card and not a QA bounce. - env_problem: your environment or seat was wrong (wrong host, stale build, no Mac runner, shared Chrome profile, expired session). A comment records it and the pass is handed off. NO FLAG and no criterion change: an environment problem is not a card defect. Check the build under test before choosing this. - blocked_dependency: an explicit prerequisite no agent can satisfy. This one flags, as kind external_dependency (a credential, consent or vendor) or owner_decision (only the owner can answer; the owner is notified). Set blocksClaim:true only for those. Every path releases the lease only after the finding is durably recorded; a claimable handoff is not a QA pass.${GOVERNED_NOTE}. It is categorised as a Execute tool in the Adrata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on record_work_item_qa_failure_and_release? +

Register the Adrata MCP server in PolicyLayer and add a rule for record_work_item_qa_failure_and_release: 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.

What risk level is record_work_item_qa_failure_and_release? +

record_work_item_qa_failure_and_release is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit record_work_item_qa_failure_and_release? +

Yes. Add a rate_limit block to the record_work_item_qa_failure_and_release 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.

How do I block record_work_item_qa_failure_and_release completely? +

Set action: deny in the PolicyLayer policy for record_work_item_qa_failure_and_release. 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.

What MCP server provides record_work_item_qa_failure_and_release? +

record_work_item_qa_failure_and_release 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.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools → High-risk tools on this server →

Across the catalogue

generate_and_execute_test on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →