AI agents use wb_input 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 registers new task dependency declarations and modifies monitoring state for artifacts. It does not execute external code (Execute), destroy data (Destructive), or involve financial transactions (Financial). It goes beyond read-only retrieval since it registers/declares dependencies and transitions artifacts into a monitoring state.
From the tool's definition Tool name 'wb_input' and description '补充申报任务依赖(gate 之外读过的登记产物,进入 stale 监控)' indicates it supplements/declares task dependencies and registers artifacts for staleness monitoring.
Attacks that exploit this kind of access
补充申报任务依赖(gate 之外读过的登记产物,进入 stale 监控). 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_input: 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_input 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_input 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_input. 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_input 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_input 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 →