wb_qa · Workbench MCP: Risk & Policy

WHAT IT DOES

What wb_qa does on Workbench

AI agents use wb_qa to create or update resources in Workbench — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Workbench environment.

WHY IT NEEDS A POLICY

Why wb_qa needs a policy

This tool writes QA acceptance data and creates side effects (automatic rework dispatch, re-verification triggers) that are reversible through normal workflow mechanisms. It does not execute arbitrary code, delete data irreversibly, or move funds.

From the tool's definition Records QA acceptance results; 'fail' automatically dispatches rework and triggers re-verification. The tool creates/modifies QA records and triggers state transitions in an artifact DAG workflow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wb_qa Rate-limited

wb_qa stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wb_qa": {
      "limits": [
        {
          "counter": "wb_qa_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Workbench, so you can run agents against it safely.

FAQ

Questions about wb_qa

What does the wb_qa tool do? +

记录 QA 验收结果;fail 必附 reason(自动派 rework,完成后自动复验). It is categorised as a Write tool in the Workbench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wb_qa? +

Register the Workbench MCP server in PolicyLayer and add a rule for wb_qa: 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 Workbench. Nothing to install.

What risk level is wb_qa? +

wb_qa is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wb_qa? +

Yes. Add a rate_limit block to the wb_qa 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 wb_qa completely? +

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

wb_qa is provided by the Workbench MCP server (nvrenshiren/workbench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

wb_qa is one line of Workbench's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →