artifact.complete_upload
Verify declared size/SHA-256 and atomically register a worker output artifact.
This record as markdown: /tools/visionmcp/artifact.complete-upload.md
What artifact.complete_upload does on Visionmcp
AI agents use artifact.complete_upload 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 artifact.complete_upload is rated Medium
This tool creates or finalizes registration of an artifact in the system, which is a reversible data creation/modification operation. It does not execute arbitrary code, delete data, or move money. While registration could have downstream effects depending on what the artifact contains, the tool itself is a write operation that commits metadata.
From the tool's definition Tool description states it 'atomically register[s] a worker output artifact' — the 'register' action creates or records data in a system. The verification step (size/SHA-256 check) is validation preceding the write operation.
Attacks that exploit this kind of access
The rule that runs artifact.complete_upload 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 artifact.complete_upload, this is the rule to start with:
artifact.complete_upload 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 artifact.complete_upload call is checked against it from then on.
Questions about artifact.complete_upload
Verify declared size/SHA-256 and atomically register a worker output artifact. 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 artifact.complete_upload: 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.
artifact.complete_upload 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 artifact.complete_upload 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 artifact.complete_upload. 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.
artifact.complete_upload 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