finalize_upload
After PUTting the file to the URL from get_upload_url, describe the asset and submit it for processing and review.
This record as markdown: /tools/3dassets-mcp/finalize-upload.md
What finalize_upload does on 3dassets
AI agents use finalize_upload to commit financial operations through 3dassets, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | |
title | string | Yes | |
aiModel | string | — | Contributor-reported model ID or custom model/tool name; use list_ai_models for suggestions. Omit if unknown. |
license | string | — | Fixed CC0 1.0 Universal dedication; no licence selection |
summary | string | Yes | Plain 1–2 sentence description |
category | string | Yes | From list_categories |
sourceUrl | string | — | Where the original was first published |
previewKey | string | — | |
aiGenerated | boolean | — | AI helped create geometry, code or textures; not merely uploading |
attestation | boolean | Yes | Required contributor acceptance (including for agent submissions): I confirm that I created this asset or hold the rights to publish it under CC0 1.0 Universal, |
description | string | — | Markdown: scale, pivot, what is included |
quarantineKey | string | Yes |
Parameters from the server's own tool schema.
Why finalize_upload is rated Critical
finalize_upload moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs finalize_upload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3dassets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For finalize_upload, this is the rule to start with:
Any call to finalize_upload is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 3dassets, apply this rule, and every finalize_upload call is checked against it from then on.
Questions about finalize_upload
After PUTting the file to the URL from get_upload_url, describe the asset and submit it for processing and review. It is categorised as a Financial tool in the 3dassets MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
finalize_upload accepts 12 parameters: tags, title, aiModel, license, summary, category, sourceUrl, previewKey, aiGenerated, attestation, description, quarantineKey. Required: title, summary, category, attestation, quarantineKey. The full parameter table on this page comes from the server's own tool schema.
Register the 3dassets MCP server in PolicyLayer and add a rule for finalize_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 3dassets. Nothing to install.
finalize_upload is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the finalize_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 finalize_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.
finalize_upload is provided by the 3dassets MCP server (3dassets-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3dassets, and thousands of servers like it.
Across the catalogue