worker.complete
Complete a leased job only after every declared output artifact is registered.
This record as markdown: /tools/visionmcp/worker.complete.md
What worker.complete does on Visionmcp
AI agents use worker.complete to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why worker.complete is rated Medium
This tool marks/completes a job and registers output artifacts, which is a write/update operation on job state. It modifies the state of a leased job and registers artifacts, but does not delete data or execute arbitrary code. The blast radius is medium because misuse could prematurely complete jobs or register incorrect artifacts, disrupting a workflow pipeline.
From the tool's definition Complete a leased job only after every declared output artifact is registered
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs worker.complete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For worker.complete, this is the rule to start with:
worker.complete 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 Visionmcp, apply this rule, and every worker.complete call is checked against it from then on.
Questions about worker.complete
Complete a leased job only after every declared output artifact is registered. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for worker.complete: 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 Visionmcp. Nothing to install.
worker.complete 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 worker.complete 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 worker.complete. 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.
worker.complete is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue