AI agents invoke wb_sync to trigger actions in Workbench. 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.
This tool performs a full reconciliation operation ('全量对账') that includes invalidation detection ('失效检测'), dispatching reviews ('review 派发'), and creating tombstones ('tombstone'). Tombstoning implies marking records as deleted/invalid (potentially irreversible state changes), and dispatching reviews triggers external pipeline operations.
From the tool's definition 全量对账:失效检测+review 派发+tombstone
Attacks that exploit this kind of access
全量对账:失效检测+review 派发+tombstone. It is categorised as a Execute tool in the Workbench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Workbench MCP server in PolicyLayer and add a rule for wb_sync: 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_sync is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wb_sync 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_sync. 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_sync 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_sync 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 →