visual_update_annotator
Update an existing visual annotation canvas session with a new image iteration (e.g., after regenerating).
This record as markdown: /tools/cowork-os/visual-update-annotator.md
What visual_update_annotator does on CoWork OS
AI agents use visual_update_annotator to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why visual_update_annotator is rated Medium
The tool modifies an existing annotation canvas by updating its image content. This is a reversible write operation (the previous iteration can be restored or overwritten again). It does not execute arbitrary code, delete data irreversibly, or trigger external operations with unpredictable effects. The blast radius is limited to the canvas state of a single session, making severity low.
From the tool's definition 'Update an existing visual annotation canvas session with a new image iteration' — this creates or modifies a canvas session reversibly by replacing an image with a new iteration.
Attacks that exploit this kind of access
The rule that runs visual_update_annotator safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For visual_update_annotator, this is the rule to start with:
visual_update_annotator 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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every visual_update_annotator call is checked against it from then on.
Questions about visual_update_annotator
Update an existing visual annotation canvas session with a new image iteration (e.g., after regenerating). It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for visual_update_annotator: 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 CoWork OS. Nothing to install.
visual_update_annotator 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 visual_update_annotator 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 visual_update_annotator. 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.
visual_update_annotator is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue