wb_update_status · Workbench MCP: Risk & Policy

WHAT IT DOES

What wb_update_status does on Workbench

AI agents use wb_update_status 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_update_status needs a policy

This is a Write operation because it modifies task status and creates reversible state changes. It rises to 'high' severity because: (1) status updates can trigger cascading effects in a multi-role pipeline (artifact DAG with 5-state trust model), (2) it may generate binding obligations/contracts ('产出义务/协议'), and (3) it activates automated checks that affect downstream agents and roles.

From the tool's definition Tool name 'wb_update_status' and description stating it 'updates task status' and triggers downstream effects: 'completed will run stale interception/output obligations/agreement lint/machine checks'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wb_update_status Rate-limited

wb_update_status 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_update_status": {
      "limits": [
        {
          "counter": "wb_update_status_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_update_status

What does the wb_update_status tool do? +

更新任务状态;completed 会跑 stale 拦截/产出义务/协议 lint/机器检查. 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_update_status? +

Register the Workbench MCP server in PolicyLayer and add a rule for wb_update_status: 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_update_status? +

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

Can I rate-limit wb_update_status? +

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

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

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