AI agents use wb_record 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.
This tool creates or modifies audit trail records and task annotations. While it records information rather than destructively altering data, it writes new entries into a system designed around approval workflows and trust contracts (evident from sibling tools like wb_audit, wb_claim, wb_dispute). The write is reversible (records can be appended, corrected, or archived) and creates traceable artifacts.
From the tool's definition Tool name 'wb_record' with description '任务备注留痕' (task notes/remarks with traceability/audit trail). The phrase '留痕' indicates recording/logging side effects, and 'wb_' prefix situates it within a workbench artifact DAG system described as managing approval…
Attacks that exploit this kind of access
任务备注留痕. 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.
Register the Workbench MCP server in PolicyLayer and add a rule for wb_record: 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.
wb_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wb_record 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 wb_record. 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.
wb_record 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.
wb_record 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 →